TeamPCP Supply Chain Attack: Telnyx PyPI Compromise and Vect Ransomware

Overview of the TeamPCP Campaign Escalation

The TeamPCP Supply Chain Attack has reached a critical inflection point following the compromise of official libraries on the Python Package Index (PyPI). According to recent findings from the SANS Internet Storm Center, the threat actors have successfully moved beyond the initial reconnaissance phase into active monetization and broad exploitation. The campaign, which originally utilized a compromised security scanner as its primary delivery mechanism, has now evolved to include the poisoning of the Telnyx Python library and the launch of the Vect Ransomware Mass Affiliate Program.

This shift represents a significant escalation in the threat actor’s capabilities, moving from a targeted infiltration strategy to a wide-scale distribution model. The use of PyPI as a distribution vector ensures that the malicious code is automatically pulled into development environments, CI/CD pipelines, and production servers that rely on these dependencies. This creates a high-trust environment for the malware to execute with the permissions of the application or service account.

The Telnyx PyPI Compromise

How to detect Telnyx PyPI compromise and malicious code

The compromise involves the injection of malicious code into versions of the Telnyx library hosted on PyPI. By subverting a legitimate package, the attackers bypass traditional perimeter defenses that might block unknown binaries but permit updates from trusted repositories. For SOC teams, the primary indicator of compromise is unusual outbound traffic from development workstations or build servers. Specifically, organizations should look for unauthorized connections to infrastructure associated with TeamPCP or the newly identified Vect C2 nodes.

Defenders must audit their requirements.txt, Pipfile, and pyproject.toml files for any references to Telnyx packages. The TTP used here mirrors previous high-profile repository attacks where legitimate functions are wrapped with secondary malicious execution blocks. These blocks typically perform environment enumeration before downloading the Vect ransomware payload. Integrating automated software composition analysis (SCA) tools into the deployment pipeline is essential for TeamPCP supply chain campaign detection and long-term resilience.

Vect Ransomware and Mass Affiliate Program

Vect Ransomware mass affiliate program mitigation and analysis

The emergence of the Vect Ransomware Mass Affiliate Program indicates that TeamPCP is adopting a Ransomware-as-a-Service (RaaS) model. This allows the core threat group to scale their operations by outsourcing the final stages of the attack—such as Lateral Movement and data exfiltration—to third-party affiliates. This development significantly increases the volume of attacks, as multiple affiliates may now be leveraging the same initial access vectors provided by the poisoned PyPI packages.

The ransomware payload itself is designed for speed and impact, often targeting backup servers and shadow copies to prevent restoration without payment. Because the delivery is initiated through a Supply Chain Attack, traditional EDR solutions may struggle to identify the initial execution if it occurs within the context of a trusted process. Consequently, defenders should focus on behavioral detection, such as mass file renaming or rapid encryption activities, and ingest all relevant IoC data into their SIEM for correlation.

Impact on Targeted Sectors and Named Victims

For the first time in this campaign, the threat actors have publicly claimed a named victim. This move signals a transition to double-extortion tactics, where stolen data is used as leverage to force payment. The diversity of the sectors affected—ranging from telecommunications to software development—underscores the indiscriminate nature of the PyPI compromise. Any organization utilizing the Telnyx API or its associated libraries is at risk.

Actionable Recommendations

To mitigate the risk of the Vect ransomware and the broader TeamPCP campaign, organizations should prioritize the following actions:

• Dependency Auditing: Freeze all PyPI updates and manually verify the integrity of the Telnyx library version currently in use. Use cryptographic hashes (SHA-256) to compare local packages against known-good versions.
• Network Segmentation: Restrict build servers and development environments from accessing the open internet. Implement a Zero Trust architecture that requires explicit allow-listing for outbound connections.
• Incident Response Readiness: Ensure that offline backups are current and that the incident response team is familiar with the recovery procedures for ransomware scenarios.
• Egress Filtering: Monitor for and block any outbound traffic to the IoCs identified in the SANS report to prevent the ransomware from reaching its command server.