The software supply chain has been under fire in 2026, with two high-profile attacks on Docker Hub targeting Trivy and Checkmarx KICS within weeks. Both incidents followed the same blueprint: stolen publisher credentials allowed malicious images to be pushed through legitimate channels, compromising users who pulled the affected tags. No infrastructure was breached, but the damage was real—secrets and internal configurations were silently exfiltrated. This article breaks down the KICS attack, what it reveals about current supply chain threats, and actionable steps to protect your pipelines. Here are five critical lessons from these events.
1. The Attack: How Stolen Credentials Enabled Malicious Images
On April 22, 2026, at approximately 12:35 UTC, a threat actor used valid Checkmarx publisher credentials to log into Docker Hub and push malicious images to the checkmarx/kics repository. Five existing tags were overwritten—latest, v2.1.20, v2.1.20-debian, alpine, debian—and two new tags (v2.1.21, v2.1.21-debian) were created. The images were built from an attacker-controlled source repository, not Checkmarx’s own. This pattern—credential theft, tag overwriting, and malicious payload delivery—mirrors the earlier Trivy compromise, highlighting a systemic vulnerability in container registry trust models.
2. The Payload: Stealthy Exfiltration Through KICS's Normal Output
The poisoned binary left KICS’s scanning functionality intact but added a quiet exfiltration path. Scan output was collected, encrypted, and sent to attacker-controlled infrastructure at audit.checkmarx[.]cx with the User-Agent KICS-Telemetry/2.0. Because KICS scans Terraform, CloudFormation, Kubernetes, and similar configuration files, its output routinely contains secrets, credentials, cloud resource names, and internal topology. The attacker exploited this legitimate data flow to siphon sensitive information without raising alarms—a classic supply chain attack where trust in a tool’s output is weaponized.
3. Which Tags Were Affected—and How to Check
Users who pulled any of the following tags during the exposure window must treat them as malicious. For alpine, v2.1.20, and v2.1.21, the index manifest digest is sha256:2588a44890263a8185bd5d9fadb6bc9220b60245dbcbc4da35e1b62a6f8c230d. For debian, v2.1.20-debian, and v2.1.21-debian, it’s sha256:222e6bfed0f3bb1937bf5e719a2342871ccd683ff1c0cb967c8e31ea58beaf7b. The latest tag digest is sha256:a0d9366f6f0166dcbf92fcdc98e1a03d2e6210e8d7e8573f74d50849130651a0. Check your Docker pull history for these digests—any match means your environment was exposed.
4. Immediate Response Actions for Affected Users
If your CI ran KICS against any repository with credentials in scope during the exposure window, rotate those credentials immediately. Repull checkmarx/kics by its digest (not by tag) to ensure you get a verified image. Pin your CI configuration to that digest so a future tag overwrite cannot silently compromise you again. Additionally, purge the malicious digests from local caches, CI runners, and pull-through registries. This multi-step response reduces the window of exposure and prevents re-infection through cached images.
5. The Bigger Picture: Why Open, Fast Collaboration Is Key
These incidents underscore the need for security teams to collaborate openly and rapidly when supply chain attacks hit. In both cases, Docker’s infrastructure was not breached—only publisher credentials were compromised. Yet the damage spread quickly because trust in container tags is implicit. The pattern calls for investment in mechanisms like cryptographic signing of images (e.g., Sigstore), automated vulnerability scanning of registry tags, and real-time alerting on unexpected tag changes. Ultimately, defending against such attacks requires a shift from trusting tags to verifying content, and from siloed response to shared intelligence.
Conclusion
The KICS and Trivy attacks are a wake-up call for anyone relying on container images from public registries. Stolen credentials can turn a trusted tool into an attack vector, and the exfiltration of secrets via legitimate output channels makes detection difficult. By understanding the attack mechanics, verifying image digests, rotating credentials promptly, and advocating for better supply chain security practices, teams can reduce their risk. The most important lesson is that speed and transparency in incident response can limit damage—something the open-source community has proven time and again.