WeSearch

Passwords stored in public Google Doc then showed up in search results

Avram Piltch· ·3 min read · 0 reactions · 0 comments · 12 views
Passwords stored in public Google Doc then showed up in search results
TL;DR · WeSearch summary

Hopefully, there’s a lesson in all this, but it could just be “stop shooting yourself in the foot.”Have a story about someone leaving a gaping hole in their network? Anonymity is available upon request.Our story today comes courtesy of Siim Kostabi, co-founder of Pageloot, a company that provides QR codes businesses can use for marketing. Kostabi’s tale of tech terror reminds us that credentials, even for a staging server, have a lot of value in the wrong hands.

Key facts
About this source

The Register publishes from United Kingdom and files mainly under tech. We currently carry 488 of its stories.

Original article
theregister · Avram Piltch
Read full at theregister →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publishertheregister
Canonical URLhttps://www.theregister.com/security/2026/08/13/passwords-stored-in-public-google-doc-then-showed-up-in-search-results/5287028
Publication timeThu, 13 Aug 2026 09:00:00 +0200
Retrieval time2026-08-13T07:30:48.301Z
Last seen2026-08-13T07:30:48.301Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterNone
Cluster logicNot yet clustered, or no peer story found in the clustering window.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); SECURITY Passwords stored in public Google Doc then showed up in search results Developer spotted hostname and credential string lurking in autocomplete Avram Piltch Avram Piltch US EDITOR US editor Published thu 13 Aug 2026 // 08:00 UTC PWNED Welcome, once again, to PWNED, the weekly column where we highlight others’ security failures.

Excerpt limited to ~120 words for fair-use compliance. The full article is at theregister.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from theregister