Ongoing 'TeamPCP' Supply-Chain Campaign
Published Sources: SingCERT
What is affected, what to do
Security researchers have identified an ongoing supply-chain campaign compromising open-source projects to distribute malware. Organisations using affected components of such projects are advised to assess their environments for potential compromise.
The available sources name no fixed version. Check the vendor guidance in the references below.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 15.53 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Security researchers have identified an ongoing supply-chain campaign compromising open-source projects to distribute malware. Organisations using affected components of such projects are advised to assess their environments for potential compromise. Security researchers have identified an ongoing supply-chain campaign attributed to ‘TeamPCP’, where open-source projects and CI/CD automation components have been compromised to distribute malware that steal credentials. The campaign reportedly first compromised Aqua Security’s open-source vulnerability scanner, Trivy, and the operation has since grown in scale to compromise other open-source projects. This advisory provides a list of known compromised project components, along with corresponding security updates that include mitigation measures and indicators of compromise. Organisations using affected components are advised to review the corresponding security updates and assess their environments for potential compromise. If a compromised version of the affected components was installed or ran in your environment, treat all secrets accessible to the environment as exposed and rotate them immediately. Trivy Trivy: v0.69.4 aquasecurity/trivy-action (GitHub Actions): All releases before v0.35.0 aquasecurity/setup-trivy (GitHub Actions): All releases before v0.2.6 Trivy Docker Image: v0.69.5, v0.69.6 Security Update: https://www.aquasec.com/blog/trivy-supply-chain-attack-what-you-need-to-know/ LiteLLM Python Package LiteLLM: 1.82.7, 1.82.8 Security Update: https://docs.litellm.ai/blog/security-update-march-2026 CheckMarx checkmarx.ast-results (OpenVSX): ast-results-2.53.0.vsix checkmarx.cx-dev-assist (OpenVSX): cx-dev-assist-1.7.0.vsix Checkmarx/kics-github-action (GitHub Actions): All releases before v2.1.20 Checkmarx/ast-github-action (GitHub Actions): All releases before v2.3.33 Security Update: https://checkmarx.com/blog/checkmarx-security-update/ NPM Multiple packages across the following namespaces: @EmilGroup @opengov @teale.io @airtm @pypestream Security Update: https://research.jfrog.com/post/canister-worm/ Telnyx Telnyx: 4.87.1, 4.87.2 Security Update: https://telnyx.com/resources/telnyx-python-sdk-supply-chain-security-notice-march-2026 This list will be updated with any other components reported to be compromised as part of the ongoing campaign.
Source: CSA/SingCERT