Checkmarx Fails Again: TeamPCP Hijacks Jenkins Plugin to Harvest Developer Credentials

Unidentified adversaries have subverted the Checkmarx plugin for Jenkins, embedding deleterious code designed for credential exfiltration. This incursion represents the latest installment in a persistent series of software supply chain attacks orchestrated by the collective known as TeamPCP.

Jenkins is utilized by thousands of enterprises to automate the compilation, testing, and deployment of software. The Checkmarx AST plugin facilitates the integration of security audits within these automated pipelines. Over the past weekend, Checkmarx issued a formal alert indicating that a modified, compromised version of the plugin had surfaced within the Jenkins Marketplace.

The corporation announced that it is currently engineering a remediated, secure iteration. The counterfeit release, designated as version 2026.5.09, was uploaded to the repo.jenkins-ci.org repository on May 9, circumventing official publication protocols. Analysts noted that the versioning deviated from established nomenclature and lacked a corresponding GitHub tag or release documentation.

TeamPCP has claimed responsibility for the breach. The group was previously implicated in the Shai-Hulud NPM attacks and the compromise of the Trivy vulnerability scanner. According to offensive security engineer Adnan Khan, the adversaries gained unauthorized access to Checkmarx’s GitHub repositories to inject the credential-harvesting payload.

A Checkmarx spokesperson confirmed that the perpetrators secured access to the repositories following the initial assault on Trivy in March. The hackers left a mocking missive within the repository description: “Checkmarx fails to rotate secrets again. With love – TeamPCP.”

Leveraging stolen credentials, TeamPCP disseminated infected versions of various developer tools across GitHub, Docker, and VSCode. The malware systematically gathered intelligence from programmer development environments. Reports suggest the group maintained persistence for at least a month, during which they successfully deployed a tainted version of the KICS tool on Docker, Open VSX, and VSCode.

Previously, in late April, Checkmarx reported that the LAPSUS$ collective had leaked data exfiltrated from its private GitHub repositories.

The company advises Jenkins administrators to verify that they are utilizing version 2.0.13-829.vc72453fa_1c16, dated December 17, 2025, or an earlier legitimate release. While precise technical details of the malicious plugin’s operation remain undisclosed, Checkmarx recommends that all access secrets be considered compromised. Users should rotate credentials immediately and scrutinize their infrastructure for signs of persistence or lateral movement.

Checkmarx clarified that its GitHub repositories remain isolated from customer production environments and that no user data was harbored within the breached repositories. The firm has published indicators of compromise (IoCs) to assist administrators in auditing their systems for traces of the offensive.