A study by researchers at Stony Brook University has revealed the alarming speed and efficiency of automated bots scanning public container registries for leaked credentials. The research found that sensitive secrets, such as AWS API keys, accidentally published within public Docker Hub images are being stolen and used maliciously in as little as 7.86 seconds. The experiment, which involved publishing honeypot images with dummy credentials, demonstrated that automated scanners, dubbed "ContainerBots," are constantly monitoring registries and can extract secrets almost instantaneously. This creates a hyper-critical risk in the software supply chain, as developers have virtually no time to react and revoke a leaked key before it is abused. The findings underscore the urgent need for both registries to implement pre-publication scanning and for developers to adopt robust secrets management practices.
The research highlights a highly automated threat targeting a common developer mistake: embedding credentials in container images. The study involved a four-month experiment where 300 honeypot images containing fake API keys for services like AWS, OpenAI, and Anthropic were published to eight public container registries.
The key findings are stark:
The threat actors are not manually searching for images; they are using automated "ContainerBots" that continuously scan newly published images.
The bots' methodology is highly efficient. Instead of pulling and running the container, which would be resource-intensive and easier to detect, they primarily use static analysis. The bots download the container image layers and scan them for patterns that match common credential formats (e.g., AWS access key IDs, secret keys). This approach allows them to analyze thousands of images rapidly and bypass runtime security controls or honeypot traps that rely on container execution.
The attack flow is simple and devastatingly effective:
Dockerfile or a file within the container image.T1552.001 - Credentials in Files. The entire attack hinges on collecting credentials left in files within container images.T1595.001 - Scanning IP Blocks. While not scanning IP blocks, the bots are performing automated scanning of a public resource (container registries).T1078.004 - Cloud Accounts. The stolen cloud keys provide the attackers with initial access to the victim's cloud environment.The impact of this threat is immediate and severe. A leaked AWS key with broad permissions could allow an attacker to:
The near-instantaneous nature of the compromise means that manual remediation is impossible. By the time a developer realizes their mistake and attempts to revoke the key, it has likely already been used. This shifts the security paradigm entirely to prevention, as post-breach response is often too late.
No specific Indicators of Compromise (IOCs) were mentioned in the source articles, as the research focused on the methodology rather than specific threat actors.
Detection must focus on both prevention and rapid post-leak response:
log_sourcelog_sourceapi_endpointCreateUser, AttachUserPolicynetwork_traffic_patternD3-LAM: Local Account Monitoring principles, but apply them to cloud identities. Monitor for anomalous behavior patterns associated with IAM users and access keys.Prevention is the only viable strategy.
D3-ACH: Application Configuration Hardening, which involves removing all hardcoded secrets from application artifacts like container images.TruffleHog, gitleaks, or commercial equivalents into your CI/CD pipeline to scan every image before it can be pushed to a registry.Preventing credentials from being embedded in container images is the primary mitigation. Use secrets management tools instead.
Educating developers about the risks of hardcoding secrets is a critical, foundational control.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.