Wiz Details TeamPCP’s Post-Compromise Activity After Supply Chain Attacks

· Original article ↗

Summary

Wiz reports that credentials stolen in TeamPCP supply chain attacks were used to explore cloud environments, execute code through GitHub workflows and AWS ECS, and exfiltrate repository and cloud data.

Key points

  • The attacks targeted Trivy, KICS, LiteLLM, and Telnyx packages or projects, with malware harvesting cloud credentials, SSH keys, Kubernetes configurations, and CI/CD secrets.
  • Wiz observed stolen credentials being validated with TruffleHog and used for AWS discovery, including enumeration of IAM, EC2, Lambda, ECS, S3, and Secrets Manager.
  • Attackers used stolen GitHub personal access tokens to create malicious workflows, access repository contents and runtime secrets, and delete workflow logs.
  • In AWS environments, attackers used ECS Exec to run commands and scripts in containers and accessed S3, Secrets Manager, and databases to retrieve data.
  • Wiz says activity appeared to originate largely from VPN exit nodes and VPS hosts; it could not rule out stolen secrets being shared with other groups.
  • Wiz advises enabling and monitoring cloud and version-control audit logs, and hunting for anomalous secret use, enumeration, mass cloning, data retrieval, and workflow-log deletion.

Article Details

Attack Vectors
  • Compromised open-source projects and packages were used to distribute credential-stealing malware through binaries, GitHub Actions, container images, OpenVSX extensions, and PyPI packages.
  • Stolen credentials and Personal Access Tokens were used to validate access, enumerate AWS environments, access running containers through ECS Exec, and create malicious GitHub workflows in targeted repositories.
  • Attackers cloned repositories and retrieved data from AWS S3 buckets, Secrets Manager, and databases; stolen secrets were also used to access additional victim resources.
Defensive Notes
  • Enable and monitor audit logging across cloud providers and version-control systems, including cloud storage logs and IP logging in GitHub audit logs.
  • Hunt for anomalous VPN use, access from new or unusual Autonomous System Organizations, cloud enumeration and secret-validation API calls, bursts of secret or object retrieval, anomalous ExecuteCommand or SSM execution, mass git.clone activity, and deleted workflow logs.
  • Review the listed network indicators and user agents, including Trufflehog, git/2.43.0, and the specified Boto3/Botocore user agent.

Indicators of compromise

TypeIndicatorContext
IPV4103[.]75[.]11[.]59Listed as a network indicator in connection with the Trivy supply-chain compromise.
IPV4105[.]245[.]181[.]120Observed callback proxy used for TruffleHog secret validation.
IPV4138[.]199[.]15[.]172Observed attacker source used for GitHub exfiltration, malicious workflow pushes, AWS reconnaissance, execution, and exfiltration.
IPV4154[.]47[.]29[.]12Observed attacker source used for secret validation and AWS reconnaissance.
IPV4163[.]245[.]223[.]12Observed attacker source used for GitHub exfiltration.
IPV4170[.]62[.]100[.]245Observed attacker source used for AWS reconnaissance.
IPV4185[.]77[.]218[.]4Observed attacker source used for TruffleHog secret validation.
IPV4193[.]32[.]126[.]157Observed attacker source used for GitHub exfiltration.
IPV4209[.]159[.]147[.]239Observed attacker source used for TruffleHog secret validation.
IPV423[.]234[.]107[.]104Observed attacker source used for TruffleHog secret validation.
IPV434[.]205[.]27[.]48Observed attacker source used for TruffleHog secret validation.

MITRE ATT&CK

Threat Actors

Vendors

Products

Tools

Related Articles