TeamPCP Compromises Checkmarx Jenkins AST Plugin Weeks After KICS Supply Chain Attack
Overview
Checkmarx has confirmed that attackers known as TeamPCP compromised the Jenkins AST plugin, altering its version before it was published to the Jenkins Marketplace. Users of the Checkmarx Jenkins AST plugin are advised to ensure they are using version 2.0.13-829.vc72453fa_1c16 or an earlier version released on December 17, 2025. This incident follows a previous supply chain attack involving KICS, raising concerns about the security of plugins within the Jenkins ecosystem. Organizations using this plugin should take immediate action to verify their version to prevent potential exploitation. The situation underscores the ongoing risks associated with third-party software components in development environments.
Key Takeaways
- Active Exploitation: This vulnerability is being actively exploited by attackers. Immediate action is recommended.
- Affected Systems: Checkmarx Jenkins AST plugin, Jenkins Marketplace
- Action Required: Ensure use of Checkmarx Jenkins AST plugin version 2.
- Timeline: Newly disclosed
Original Article Summary
Checkmarx has confirmed that a modified version of the Jenkins AST plugin was published to the Jenkins Marketplace. "If you are using Checkmarx Jenkins AST plugin, you need to ensure that you are using the version 2.0.13-829.vc72453fa_1c16 that was published on December 17, 2025 or previously," the cybersecurity company said in a statement over the weekend. As of writing, Checkmarx has released
Impact
Checkmarx Jenkins AST plugin, Jenkins Marketplace
Exploitation Status
This vulnerability is confirmed to be actively exploited by attackers in real-world attacks. Organizations should prioritize patching or implementing workarounds immediately.
Timeline
Newly disclosed
Remediation
Ensure use of Checkmarx Jenkins AST plugin version 2.0.13-829.vc72453fa_1c16 or earlier.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.