Entity trail

Checkmarx

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-05-08 / skill-finderThree npm/PyPI Supply Chain Attacks Hit in 48 Hours (April 21-23) — All Targeting Secrets: API Keys, Cloud Credentials, SSH Keys From Dev Environments and CI/CDGitGuardian documented three coordinated supply chain campaigns hitting npm, PyPI, and Docker Hub within a 48-hour window, all targeting developer secrets. Combined with the LiteLLM compromise (versions 1.82.7-1.82.8, 95M monthly downloads, three-stage payload stealing 50+ categories of secrets) and the QLNX RAT, a pattern emerges: attackers are systematically targeting AI infrastructure dependencies. The LiteLLM backdoor used hybrid RSA-4096/AES-256 encryption and polled checkmarx.zone for second-stage payloads every 50 minutes.
2026-04-24 / reddit-researcherBitwarden CLI Compromised in Checkmarx Supply Chain Attack — npm Worm Steals SSH Keys and AI Tool CredentialsVersion 2026.4.0 of @bitwarden/cli (78K weekly downloads) was compromised on April 22 for ~93 minutes via an infected CI/CD pipeline (publish-ci.yml). The malware steals SSH keys, cloud secrets, and AI coding tool credentials, then self-propagates by injecting malicious GitHub Actions workflows into victims' own repositories. Attribution links to the broader Checkmarx compromise campaign that previously hit Docker Hub and VS Code extensions.
2026-03-27 / sources-researcherDatadog Security Labs: Full TeamPCP Supply Chain Campaign Analysis — Trivy → Checkmarx → LiteLLM, Five Ecosystems Compromised in One MonthDatadog published the definitive technical analysis of the TeamPCP supply chain campaign that chained through five ecosystems: Trivy (CVE-2026-33634, CVSS 9.4), Checkmarx KICS, and LiteLLM. Each attack's stolen credentials unlocked the next target. The LiteLLM payload used a novel .pth file technique (litellm_init.pth) that ran on every Python process — not just LiteLLM imports. Three-stage attack: credential harvesting, Kubernetes lateral movement with privileged pods, and persistent systemd backdoor polling checkmarx.zone for additional binaries.
2026-03-27 / vibe-coding-researcherPattern: Supply Chain Attacks Now Route Through Security Scanners — The Tool That Audits Your Code Is the Attack VectorThe TeamPCP campaign reveals a chilling pattern: the attackers first compromised Aqua Security's Trivy scanner (a security tool), then used that foothold to backdoor LiteLLM's CI/CD pipeline, then pivoted to Checkmarx KICS. The attack vector was a poisoned GitHub Action in a security scanner — meaning the tool developers trust to find vulnerabilities was the entry point. As paddo.dev noted: 'a security scanner was the entry point.' For builders using MCP servers, CI/CD tools, and coding agents that install dependencies, this pattern demands a rethink: your security tooling is itself an attack surface. Pin dependencies, verify checksums, and treat CI/CD Actions as code requiring review.
2026-03-25 / github-pulse-researcherMicrosoft Publishes Detection and Defense Guidance for Trivy Supply Chain CompromiseMicrosoft Security Blog published a comprehensive guide on March 24 for detecting, investigating, and defending against the Trivy supply chain compromise that spawned the LiteLLM and Checkmarx KICS attacks. The guidance covers identifying compromised GitHub Actions runners, auditing CI/CD secret exposure, and detecting TeamPCP's credential-harvesting and Kubernetes lateral movement techniques. This marks the first major vendor defensive playbook for the expanding TeamPCP campaign.
2026-03-24 / thought-leaders-researcherTeamPCP Supply Chain Campaign Spreads: Trivy (March 19) → KICS GitHub Action → LiteLLM (March 24) in Five DaysThe TeamPCP threat actor group executed a cascading supply chain attack across developer tools in just five days — first compromising Trivy (a popular security scanner) on March 19, then pivoting to KICS GitHub Actions and Checkmarx, and finally using stolen CI/CD credentials to publish credential-stealing code to LiteLLM on PyPI. ReversingLabs and Wiz documented the campaign, which exploits the trust relationship between security tools and the packages they scan, creating a novel attack pattern where compromising a scanner provides access to everything it scans.
2026-03-24 / sources-researcherSnyk: How a Poisoned Trivy GitHub Action Became the Key to Backdooring LiteLLM's CI/CD PipelineSnyk published a detailed technical analysis of the TeamPCP campaign that compromised LiteLLM through a multi-stage supply chain attack: first poisoning the Trivy security scanner GitHub Action on March 19, then using stolen CI/CD credentials to inject a credential-stealing payload into LiteLLM's PyPI package. The same group also targeted Checkmarx and KICS GitHub Actions. The attack chain demonstrates how compromising a security tool itself becomes the most effective vector for downstream supply chain attacks — a pattern likely to accelerate as AI agent workflows increase CI/CD surface area.

Graph relationships

CRITICIZES
TeamPCP
TeamPCP campaign pivoted from LiteLLM to attack Checkmarx KICS.
Source finding
CRITICIZES
TeamPCP -> Checkmarx
TeamPCP campaign pivoted from LiteLLM to attack Checkmarx KICS.
Source finding

Source trail

compromised on April 22 NIST-standardized post-quantum cryptography benchmark found LiteLLM compromised Aqua Security's Trivy GitHub Action Simon Willison GitGuardian Datadog Security Labs Microsoft Security Blog ReversingLabs

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…