Skip to main content
Diagram: how an unencrypted object store exposed Kik profile images before access was closed. Illustration: SecurityXP

Kik Profile Images Exposed in Open Database, Researcher Says

· 4 min read · SecurityXP Editorial Desk

Key Facts

  • Security researcher Jeremiah Fowler found an unencrypted, publicly accessible database containing more than 150 million profile images associated with Kik.
  • About 75 million of the images were original, high-resolution photos uploaded between 2021 and 2026, according to SC Media's account of the finding.
  • The database was secured after disclosure; how long it remained exposed is not known.
  • Fowler reported that a sample of the images contained child sexual abuse material, and notified the National Center for Missing and Exploited Children and the Connecticut attorney general.
  • Kik, owned by MediaLab, did not comment on the incident, according to SC Media.

A security researcher has found an unencrypted, publicly accessible database containing more than 150 million profile images associated with Kik, the messaging app owned by MediaLab. The database was secured after the researcher disclosed it, but how long it remained open — and who may have accessed it — is not known.

The finding, reported by SC Media and TechRadar, is a familiar cloud-storage failure with an unusually sensitive set of files. It also raises questions about age assurance and content moderation on a platform that has spent years trying to distance itself from its reputation as a haven for minors and bad actors.

What was exposed

Jeremiah Fowler, the researcher credited with the discovery, said the collection was not password-protected and could be reached from an ordinary web browser. According to SC Media’s account, it held more than 150 million profile images, including roughly 75 million original, high-resolution photos uploaded between 2021 and 2026.

The files were profile images rather than private messages, but profile photos can still reveal a great deal: faces, usernames, social connections, and in some cases location clues in the background. A large image set also creates a ready-made training corpus for facial recognition or impersonation, even if no passwords were included.

Fowler told SC Media that the database was secured after he reported it. The exposure window remains unknown, which means there is no reliable way to say whether anyone else found the files first.

The child-safety finding

The most serious allegation is that a sample of the images contained child sexual abuse material. Fowler reported the sample to the National Center for Missing and Exploited Children and to the Connecticut attorney general, according to SC Media.

That reporting path is the correct one. Platforms and researchers should not redistribute suspected CSAM, describe it in detail, or attempt to identify the people depicted. The public interest is in the handling of the report, the preservation of evidence and the platform’s response, not in the content itself.

The finding also complicates the usual “no passwords, no harm” framing. A profile image can be harmful on its own when it depicts a minor, when it is reused for impersonation, or when it is pulled into a facial-recognition dataset.

Kik’s response

Kik is owned by MediaLab. SC Media reported that the company did not comment on the incident. That leaves several questions open: whether Kik or a third-party vendor operated the database, what access logs exist, whether affected users will be notified, and whether the company has reported the matter to regulators beyond the researcher’s own notification.

Kik updated its terms of service in 2025 to restrict use to people 18 and older. The exposed data reportedly included images of individuals who appeared to be minors. Age rules are not the same as age assurance, and neither is a substitute for content moderation or access control on stored images.

A cloud configuration problem

The mechanics here are not exotic. Object storage is easy to provision and easy to misconfigure. A bucket can be made public for a launch, a migration or a support workflow, and then left open long after the project ends.

The controls that prevent this are well known:

  • Default-deny bucket policies, with public access treated as an exception that expires.
  • Separate storage accounts for public assets and user uploads.
  • Lifecycle rules that delete data the business no longer needs.
  • Access logging and anomaly alerts on object reads.
  • A pre-production check that scans for public buckets and unauthenticated endpoints.
  • A named owner for every bucket, not just a project team.

None of these requires a new product. They require someone to own the configuration and someone to check it after the next migration.

What should happen next

The immediate priorities are containment, notification and an independent account of what happened. Users whose images were exposed should be told what was stored, for how long it was reachable, and what the platform is doing about it. Regulators should be able to verify the timeline rather than rely on a press statement.

For Kik, the harder question is structural. A platform that hosts a large volume of user-uploaded images needs a retention policy, a content-classification pipeline and a tested escalation path for suspected CSAM. Those are not optional features bolted on after a breach; they are the operating model.

For every other platform, the lesson is simpler: an open bucket is not a hypothetical. It is a configuration mistake that can sit unnoticed for years, and the data inside it does not have to include a password to cause serious harm.

Tags: Kik MediaLab Jeremiah Fowler Data Breach Cloud Storage Child Safety Content Moderation

Sources & References

SE SecurityXP Editorial Desk
SecurityXP Editorial Desk Vulnerability Research & News Board

Automated and analyst-reviewed threat intelligence briefings tracking active exploitation campaigns, CVE disclosures, and extortion group activity.

Security Digest

The most important cybersecurity stories, CVE alerts, and threat intelligence — one concise email. Unsubscribe anytime.

Related Articles

Timeline of 3 events, 2026-07-06 to 2026-11-04; disruption at 2026-11-04.
Data Breaches

Highland Shores Children's Aid Says Intruder Took Personal Files in July Breach

An Ontario children's aid society says an intruder accessed its network on July 6 and took files with names, SINs, medical and child-welfare records. Regulators and police were notified.

Process diagram of the data breach path: business mail through 22M records exposed, with the fault at mid-Sept intrusion.
Data Breaches

La Poste Subsidiary Maileva Discloses Breach of 22 Million Recipients' Names and Addresses

Maileva, a Docaposte subsidiary of La Poste, confirmed a mid-September intrusion that exposed first names, last names, and postal addresses for 22 million mail recipients.

Process diagram of the data breach path: System intrusion through Forum sale, with the fault at Franchisee docs.
Technology

7-Eleven Data Breach: 185,000 People Exposed

The ShinyHunters extortion gang claimed responsibility, leaked a 9.4GB archive of stolen data, and is now selling it on underground forums after the company refused to pay a ransom.

Process diagram of the data breach path: Credential theft through Data exfiltration, with the fault at Credential theft.
Technology

Carnival Data Breach Impacts 6 Million Customers

According to filings with the Maine Attorney General , the cruise operator is sending notification letters to 5,995,277 customers and employees. Hackers got in and exfiltrated sensitive files.