Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Container Honeypots Show Exposed Cloud Keys Being Used Within Eight Seconds

An ACM CCS 2026 study tracks deliberate credential exposure in container images, showing why release checks and rapid revocation matter for cloud secrets.

Container Honeypots Show Exposed Cloud Keys Being Used Within Eight Seconds
PUBLISHED

Research briefing: November 18, 2026. The ContainerBots project abstract describes a four-month experiment using 300 instrumented container images across eight public registries. Researchers planted test credentials and observed subsequent activity.

The researchers report secrets being extracted and used as quickly as eight seconds after publication. Their AWS honeytokens received more than 140,000 API calls from over 5,000 unique IP addresses; test AI-service balances were consumed in short bursts. These were deliberately exposed credentials in a research experiment, not 300 identified production breaches.

What the result establishes

The fastest observation is not a universal time-to-compromise estimate. The abstract does not establish that every image attracts identical activity or that all observed IP addresses belong to one operator. The paper Gone in 8 Seconds appears in the ACM CCS 2026 programme. This briefing relies on the abstract; IPCRIME has not reproduced the experiment.

IPCRIME analysis: move the check before publication

Treat an image as a release artifact that needs its own review. A clean source repository does not, by itself, answer what the completed image contains. Make ownership explicit: someone should be responsible for checking the artifact and deciding what happens when that check fails.

Docker’s build documentation warns against passing build secrets through arguments or environment variables because they persist in the final image. It describes secret and SSH mounts as the appropriate build-time mechanisms, with secret mounts available temporarily during the build instruction.

For an exposed credential, deleting a public image cannot establish that previously retrieved copies disappeared. Identify the account and permissions involved, revoke or rotate the credential, and inspect available account activity. Record both the publication window and the completed revocation.

Use the finding to shorten the gap between detection and containment, while keeping the preventive gate ahead of publication. A cleanup process that begins only after a developer notices the mistake leaves an avoidable period of exposure.

Related reading: Digital Arsenal: Audit Vendor Keys and Exposed Secrets With Open-Source Tools.

Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.