Backdoored Jenkins Plugin Signals Escalation in TeamPCP Supply Chain Campaign

A fresh compromise of a widely used CI/CD security integration is raising new alarms about the persistence and sophistication of modern software supply chain attacks. SOC Radar researchers are warning that the threat actor known as TeamPCP has once again infiltrated infrastructure tied to Checkmarx, this time targeting its plugin for Jenkins.

The incident centers on a backdoored release of the Checkmarx Jenkins plugin, a tool designed to embed application security testing directly into developer pipelines. According to publicly shared findings, attackers not only tampered with the plugin’s distribution but also defaced its source repository in a move that blends signaling with exploitation.

A Trusted Tool Turned Attack Vector

The compromised plugin version, identified as 2026.5.09, was briefly available through official distribution channels. Any organization that pulled updates during that window may have unknowingly installed malicious code into their CI pipelines.

This is what makes the attack particularly dangerous. Jenkins plugins often operate with deep access to build environments, including source code, credentials, and deployment pipelines. By embedding malware into a trusted security tool, attackers effectively bypass traditional defenses and inherit privileged access across multiple systems.

Security researchers note that the malicious payload appears to follow a familiar pattern seen in earlier TeamPCP campaigns. Once deployed, it can scan for sensitive data such as API keys, cloud credentials, SSH keys, and Kubernetes tokens, then package and exfiltrate that data to attacker-controlled infrastructure.

“Dune-Themed” Malware and a Familiar Signature

The attackers left behind a distinct calling card. Repositories tied to the breach featured references to the science fiction universe of Dune, with code names and descriptions hinting at coordinated tooling. This aligns with previous TeamPCP operations, where themed naming conventions were used to track and organize malicious components.

The public defacement of the repository also included a pointed message suggesting failures in credential rotation practices. While taunts from attackers are not always reliable indicators, they often highlight real weaknesses that enabled the intrusion.

A Pattern of Re-Entry

This latest breach is not an isolated event. TeamPCP previously compromised Checkmarx assets earlier in 2026, including GitHub Actions and developer tooling integrations. That earlier campaign focused on harvesting secrets from CI environments, using malicious updates to propagate across developer workflows.

The reappearance of the same actor in a similar environment suggests one of two scenarios. Either remediation efforts failed to fully close the initial access points, or the attackers successfully maintained persistence inside the ecosystem.

For defenders, that distinction matters less than the implication. Supply chain attackers are no longer operating as one-time opportunists. They are returning, probing, and exploiting gaps over time.

The Expanding Risk to CI/CD Environments

The incident underscores a growing reality in cybersecurity. CI/CD systems are now prime targets because they sit at the intersection of code, infrastructure, and secrets.

Compromising a single plugin can cascade into widespread access across development and production systems.

In practical terms, any organization using the affected plugin version should assume potential exposure of credentials and sensitive data. That includes tokens tied to GitHub, AWS, Azure, GCP, container registries, and internal services.

Immediate Actions for Security Teams

Security teams are being urged to take rapid containment steps:

• Audit Jenkins environments for the affected plugin version

• Rotate all credentials accessible to CI runners

• Review build logs for suspicious outbound connections

• Search for indicators tied to the attacker’s tooling and naming patterns

• Pin dependencies to verified versions and validate integrity before deployment

Longer term, experts recommend moving toward short-lived credentials, enforcing least privilege access, and treating CI/CD infrastructure with the same level of scrutiny as production systems.

The Bigger Picture: Trust Is the Target

This attack highlights a fundamental shift in how threat actors approach enterprise environments. Rather than attacking endpoints directly, they are targeting the trust relationships that underpin modern software development.

When a security tool becomes the attack vector, it forces organizations to rethink assumptions about trusted components. The question is no longer whether a tool is designed for security, but whether its supply chain can be trusted at all times.

As supply chain attacks continue to evolve, visibility into third-party dependencies and real-time monitoring of vendor risk will become essential. Without it, even the tools meant to protect systems can quietly become the point of compromise.