✨ The Containment Era is here. →Explore ✨

aviatrix logoAviatrix

Overview

Threat intelligence hub

Command Center

Visualize blast radius & threats

Under Active Attack

Executive Summary

In March 2026, the threat actor TeamPCP executed a sophisticated supply chain attack by compromising the Telnyx Python SDK on the Python Package Index (PyPI). Malicious versions 4.87.1 and 4.87.2 were published, embedding payloads within WAV audio files—a novel steganography technique. These payloads targeted Windows systems by dropping a persistent binary named 'msbuild.exe' into the Startup folder, while Linux and macOS systems faced credential harvesting similar to previous LiteLLM compromises. Forensic analyses confirmed the use of RSA-4096 encryption and specific exfiltration patterns consistent with TeamPCP's tactics. The compromised versions were promptly quarantined by PyPI. Concurrently, TeamPCP partnered with the Vect ransomware-as-a-service operation and BreachForums, distributing affiliate keys to approximately 300,000 users, potentially enabling one of the largest coordinated ransomware deployments observed. Additionally, the LAPSUS$ group claimed a 3GB data breach of AstraZeneca, allegedly using credentials obtained through TeamPCP's activities. This breach reportedly includes internal code repositories, cloud infrastructure configurations, and employee data. Organizations affected by any phase of the TeamPCP campaign are urged to rotate credentials immediately and monitor for indicators of compromise.

Why This Matters Now

The convergence of supply chain compromises, ransomware-as-a-service models, and dark web forum mobilization signifies an unprecedented escalation in cyber threats. Organizations must proactively secure their software supply chains and implement robust monitoring to mitigate these evolving risks.

Attack Path Analysis

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

The use of WAV steganography allowed TeamPCP to conceal malicious payloads within audio files, making detection more challenging and demonstrating an evolution in obfuscation tactics.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Aviatrix Zero Trust CNSF is pertinent to this incident as it could have limited the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and controlled egress policies.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: The CNSF may have constrained the attacker's ability to exploit the compromised SDK by enforcing strict workload isolation and identity-aware routing.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust Segmentation would likely have restricted the malware's ability to escalate privileges by enforcing least-privilege access controls.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-West Traffic Security may have constrained the malware's lateral movement by monitoring and controlling internal traffic flows.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Multicloud Visibility & Control would likely have identified and restricted unauthorized outbound connections to attacker-controlled domains.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress Security & Policy Enforcement may have limited the exfiltration of sensitive data by enforcing strict outbound traffic policies.

Impact (Mitigations)

The implementation of CNSF controls would likely have reduced the overall impact by limiting unauthorized access and constraining the attacker's ability to exploit compromised credentials.

Impact at a Glance

Affected Business Functions

  • Software Development
  • Continuous Integration/Continuous Deployment (CI/CD) Pipelines
  • Credential Management
  • Supply Chain Security
Operational Disruption

Estimated downtime: 7 days

Financial Impact

Estimated loss: $500,000

Data Exposure

Compromised credentials, including SSH keys, cloud tokens, Kubernetes secrets, and crypto wallets, leading to potential unauthorized access and data breaches.

Recommended Actions

  • • Implement Zero Trust Segmentation to restrict lateral movement within Kubernetes clusters.
  • • Enforce Egress Security & Policy Enforcement to monitor and control outbound traffic to prevent data exfiltration.
  • • Deploy Threat Detection & Anomaly Response systems to identify and respond to malicious activities promptly.
  • • Utilize Multicloud Visibility & Control to gain comprehensive insights into cloud environments and detect anomalies.
  • • Regularly audit and rotate credentials to mitigate the risk of unauthorized access due to compromised credentials.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Stop Advanced ThreatsGet a Free Workload Attack Path AssessmentUnder Active Attack?
Cta pattren Image