Nine million faces in an open bucket, and the vendor's answer was "the URL wasn't indexed"
A researcher found 450GB of uploaded photos with no authentication in front of them at US lookup service ClarityCheck. A face, unlike a password, cannot be reset.
The Watch · Security desk
What happened
- A researcher reported finding nearly 9.1 million facial images in an unsecured database belonging to US company ClarityCheck.
- ClarityCheck sells a reverse image search that promises to identify anyone in a photo and return names, social profiles and online presence.
- The 450.2 GB store held profile images, screenshots and photographs of adults, teens and children, kept unencrypted.
- Access was restricted only after WIRED contacted the service in July; earlier alerts from the researcher had not produced a fix.
Why it matters
- Who's exposed exposure Uploads are gated by a self-attestation checkbox that nobody can verify, so the exposed population includes people who never used the service and never got a say in who stored their face.
- What it limits constraint There is no rotation path for a face, so the remedy for anyone in this bucket is manual delisting and takedown requests rather than a credential reset that closes the issue.
- Who has to decide decision Any internal workflow that ships staff or customer photos to a lookup or verification vendor now needs retention, deletion, model-training and third-party sharing answers on paper before the first...
- What doesn't add up contradiction Researchers call the contents facial biometrics while the company says it does not use facial recognition, and that label decides whether the files get handled as sensitive personal data or as...
Next story · Product · Aug 19
A "private and secure" face search left 9 million images in an open bucketConfirmed3 publishers
Divide 450.2 GB by 9.1 million files and the average image works out at roughly 49 KB [18]. That is not a vault of high-resolution portraits; it fits what was reported in the store, profile pictures and screenshots [8]. Small files, but each one is the input side of a lookup: a photo someone pasted in to get back a name, social profiles and an online presence [1].
ClarityCheck's position, according to Malwarebytes' account, is that this was not a public exposure because reaching the files required an unindexed URL [9]. Unindexed and unreachable are different properties. Fowler obtained the URLs from the site's own code [9], which is the point at which obscurity stops being a control and becomes a description of how the storage was addressed. Nothing in the path asked for authentication [5].
The company also says it does not use facial recognition, while describing its image function as a way to identify people and find their names and social profiles [2]. For anyone whose photo is in the bucket, that distinction is a matter of internal architecture. What an attacker takes away is an image tied to a name, social accounts, and possibly an address, email or phone number, which is the raw material for impersonation, targeted phishing, doxxing and catfishing [13].
How long the store was open before Fowler found it is unknown [10]. That gap is the expensive part. Without a bounded window, nobody can scope who to notify or say whether a given face was copied, so there is no version of this incident in which the affected people get a clean answer. They were never the customers anyway; they were the query.
Fowler implies no wrongdoing by ClarityCheck and makes no claim of active exploitation, calling the risk hypothetical [15]. That caveat is worth keeping in view, because the failure on record is a storage decision rather than a theft. It is also the reason the story matters to anyone buying identity tooling: the same company sells reverse image search and identity verification [7], and the security floor under the verification data turned out to be an unlisted address. Fowler's own standard is the one to hold vendors to, which is that firms collecting facial biometric data should treat it as sensitive personally identifiable information and protect it accordingly [16].
What to watch
- Whether ClarityCheck publishes an exposure window or access logs that would let affected people know if their image was copied.
- Whether the company changes the "we do not use facial recognition" description now that its store has been characterised as facial biometrics.
- Whether the same researcher method, reading storage URLs out of front-end code, turns up open buckets at other people-finder and verification services.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+15
- Incentives45
- Confidence60
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
ClarityCheck describes its service as: "Use reverse image search to identify anyone in a photo. Find names, social profiles, and online presence in seconds."
- [2]
ClarityCheck says it does not use facial recognition, but describes its image function as a way to identify people and find their names and social profiles.
- [3]
Researcher Jeremiah Fowler discovered an unsecured database containing nearly 9.1 million facial images belonging to U.S. company ClarityCheck, according to Biometric Update.
- [4]
The ClarityCheck database housed approximately 450.2 GB of data.
- [5]
Fowler found a cloud database containing more than 9 million image files accessible without authentication, and the bucket held some 450 GB of images, WIRED reports.
- [6]
The leaky bucket was traced back to a US-registered company called ClarityCheck.
- [7]
ClarityCheck offers reverse image search and identity verification services.
- [8]
The exposed data included profile images, screenshots and photographs of adults, teens and children, stored unencrypted and without adequate security safeguards.
- [9]
ClarityCheck disputed that the data was publicly exposed because accessing it required an unindexed URL; however the images did not require authentication and Fowler was able to discover the URLs through the site's code.
- [10]
It is unknown how long the bucket was exposed before Fowler found it.
- [11]
Despite earlier alerts from Fowler, ClarityCheck did not restrict access to the database until WIRED contacted the service in July.
- [12]
Faces are persistent identifiers: a leaked password can be reset, whereas a person cannot easily replace their face.
- [13]
When an image of someone is linked with names, social profiles, addresses, emails or phone numbers, that information could be misused for impersonation, targeted phishing, doxxing or catfishing.
- [14]
ClarityCheck and many similar tools require users to confirm that they own the image, appear in it, or otherwise have the necessary rights to upload it, but a checkbox cannot prevent someone from lying.
- [15]
Fowler implies no wrongdoing by ClarityCheck and does not claim active exploitation, saying the exposed data poses a hypothetical risk.
- [16]
Fowler stressed that companies collecting facial biometric data should treat it as sensitive personally identifiable information and protect it accordingly.
- [17]
Malwarebytes advises checking any such service's policies on image retention, deletion, AI model-training use, storage, third-party sharing and image removal before using it.
- [18]
The exposed files average roughly 49 KB each.
Sources
2 independent publishers whose own reporting we read for this story.
- malwarebytes.com9 million images of people’s faces exposed by reverse lookup service
1 article · August 20, 2026
- scworld.comUnsecured database exposes millions of facial biometrics
1 article · August 20, 2026
Topics and entities
Topics
- Reverse image search
- People search services
- Cloud Storage Misconfiguration
- Biometric Privacy
Entities
- Biometric Update
- Wired
- Malwarebytes