CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-12
HIGHupdatedNATOA2threat

Checkmarx Jenkins AST plugin backdoored: rogue build 2026.5.09 swept build hosts for credentials on 2026-05-09/10, the third wave of malicious Checkmarx artifacts since March (TeamPCP claimed)

A rogue Checkmarx Jenkins AST plugin build that hunts credentials was live for about 31 hours; TeamPCP claimed it

Analysis

On Saturday 2026-05-09 a rogue build, version 2026.5.09, of the Checkmarx Jenkins AST plugin was uploaded to repo.jenkins-ci.org outside the plugin's release pipeline; it broke the plugin's version scheme and had no git tag or GitHub release (BleepingComputer, 2026-05-11). Checkmarx says an external service account modified the plugin and published it to the Jenkins Marketplace, that the malicious window ran from 2026-05-09 01:25 UTC to 2026-05-10 08:47 UTC, and that the attacker used access obtained in the March incident, which began with credentials taken in the Trivy supply-chain attack on 2026-03-19 (Checkmarx, updated 2026-07-06). It is the third wave of malicious Checkmarx artifacts after GitHub Actions and Open VSX extensions on 2026-03-23 and a KICS Docker image, VS Code and DevAssist extensions and a GitHub Action on 2026-04-22 (Checkmarx, updated 2026-07-06). The payload determines the operating system (Windows, Linux or macOS), then walks a list of file paths for common applications on that system looking for credentials, with crypto wallets, VPNs, AWS and GitHub among the targets; Checkmarx had found no references to Jenkins in it, and Mandiant found no threat-actor access to the Checkmarx One SaaS environment (Checkmarx, updated 2026-07-06).

TeamPCP claimed the compromise (BleepingComputer, 2026-05-11), and researcher Adnan Khan and SOCRadar report that the group gained access to the plugin's GitHub repository and renamed it "Checkmarx-Fully-Hacked-by-TeamPCP-and-Their-Customers-Should-Cancel-Now", with the description "Checkmarx fails to rotate secrets again. with love – TeamPCP" (The Hacker News, 2026-05-11). Google Threat Intelligence Group tracks TeamPCP as UNC6780 and says that in the late-March compromises (Trivy, Checkmarx, LiteLLM, BerriAI) the group embedded the SANDCLOCK credential stealer to extract cloud secrets such as AWS keys and GitHub tokens from build environments (GTIG, 2026-05-11).

Cited evidence

The malicious window was 2026-05-09 01:25 UTC to 2026-05-10 08:47 UTC.

Our assessment based on currently available evidence is that the threat actor was able to leverage access, obtained as part of the March incident, to later publish the modified version of the Jenkins plugin on May 9.

Targeted applications include crypto wallets, VPNs, AWS, and Github.

Checkmarx 2026-07-06

The compromise was claimed by the TeamPCP hacker group

The update was outside the plugin's release pipeline and included malicious code.

BleepingComputer 2026-05-11

Updates1

Correction

No CVE covers the rogue plugin build: CVE-2026-33634 is the Trivy flaw in which a threat actor used compromised credentials on 2026-03-19 to publish a malicious Trivy release and move the trivy-action tags to credential-stealing code (GitHub Advisory Database, 2026-03-21), the attack Checkmarx names as the source of the attacker's access (Checkmarx, updated 2026-07-06). No source names SANDCLOCK as the Jenkins payload; GTIG uses the name for the stealer of the late-March compromises and describes it extracting cloud secrets such as AWS keys and GitHub tokens, not LLM API keys (GTIG, 2026-05-11). Checkmarx lists crypto wallets, VPNs, AWS and GitHub among the applications the payload targets, and Mandiant found no threat-actor access to the Checkmarx One SaaS environment (Checkmarx, updated 2026-07-06).

The earlier waves were GitHub Actions and Open VSX extensions in March and the KICS Docker image with updated extensions and a GitHub Action in April (Checkmarx, updated 2026-07-06). PCPJack is a separate cloud worm whose first act is to evict TeamPCP tooling (SentinelLABS, 2026-05-07), and no cited source links it to the plugin. The defacement renamed the plugin's GitHub repository, not the build (The Hacker News, 2026-05-11), and exposure did not depend on auto-update: any instance that pulled build 2026.5.09 during the window installed the compromised plugin (SOCRadar, 2026-05-11).

Sources7

Revision history

  1. Published 2026-05-12-cd1ab844
  2. Correction 2026-10-21T1148Z-audit

    CVE-2026-33634 is the March 2026 Trivy malicious-release flaw, not a CVE for the Checkmarx Jenkins plugin, and no source names SANDCLOCK as the Jenkins payload, which Checkmarx says sweeps file paths for credentials of crypto wallets, VPNs, AWS and GitHub. The March wave was GitHub Actions and Open VSX extensions and the KICS Docker image came in April; the PCPJack worm, LLM API key targeting and Checkmarx One API tokens are not part of this incident. Exposure covers any instance that installed build 2026.5.09 between 2026-05-09 01:25 and 2026-05-10 08:47 UTC, and TeamPCP's role rests on its own claim.

    Changed: affected_products body classification cves entities event_date evidence headline kind regions sources sourcing_note summary tags techniques title

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.