CriticalDocker7 affected versions

checkmarx/kics

checkmarx/kics has 7 versions on Docker Hub flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with docker image ls.

checkmarx/kics@latest
checkmarx/kics@debian
checkmarx/kics@alpine
checkmarx/kics@2.1.21-debian
checkmarx/kics@2.1.21
checkmarx/kics@2.1.20-debian
checkmarx/kics@2.1.20

The incident that flagged it

Critical22 Apr 2026

Checkmarx KICS Docker images + Open VSX extensions compromised (TeamPCP)

Docker and Socket jointly disclosed a multi-stage compromise of Checkmarx KICS Docker images and Checkmarx VS Code / Open VSX extensions. Trojanised extensions silently install an MCP addon executed via Bun, while the Docker images include a modified KICS binary that encrypts scan output and exfiltrates it. TeamPCP claimed responsibility.

Versions named here: 2.1.20, 2.1.20-debian, 2.1.21, 2.1.21-debian, alpine, debian, latest

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

checkmarx/kics is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse Docker manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged Docker packages

Other packages in the same incident

If checkmarx/kics is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.