TeamPCP Hacks Telnyx Package, Hides Malware in WAV Files

Michael Miller · 2026-03-27

You know how you sometimes download a Python package without thinking twice? Well, that's exactly what the TeamPCP threat actors are banking on. They've just pulled off another supply chain attack, and this time they've compromised the telnyx Python package. It's a stark reminder that even trusted repositories like PyPI aren't immune to these sophisticated attacks. Let's break this down. TeamPCP isn't some random hacker. This is the same group behind those attacks on Trivy, KICS, and litellm earlier this year. They've got a pattern, and they're sticking to it. Their latest move? Pushing two malicious versions of the telnyx package to PyPI on March 27, 2026. ### The Malicious Versions You Need to Know The compromised versions are 4.87.1 and 4.87.2. If you've installed either of these, you need to act fast. The packages look legitimate on the surface, but they're hiding something dangerous inside. What makes this attack particularly clever is the delivery method. Instead of obvious malicious code, TeamPCP concealed their credential-harvesting malware within a .WAV audio file. That's right—they hid a digital thief inside what looks like a simple sound file. It's like finding a burglar hiding in your music library. ### How the WAV File Stealer Works This isn't your average malware. The code embedded in the WAV file is designed to steal sensitive data from your system. We're talking about credentials, API keys, configuration files—anything that could give attackers access to your systems or accounts. The attack works because most security tools don't deeply inspect WAV files for executable code. It's an old trick, but it keeps working because we don't expect audio files to be dangerous. As one security researcher recently noted, "The most effective attacks often exploit our assumptions about what's safe." Here's what you should check immediately: - Your Python environment for telnyx versions 4.87.1 or 4.87.2 - Any systems that might have automatically updated to these versions - Your credential storage and whether any sensitive data has been accessed ### Why This Attack Matters for Developers If you're thinking "I don't use telnyx, so this doesn't affect me," think again. This attack reveals broader vulnerabilities in our development ecosystems. PyPI is one of the most trusted repositories for Python developers, serving millions of packages daily. When attackers can compromise packages there, it puts everyone at risk. The real danger isn't just this specific attack—it's what it represents. Supply chain attacks are becoming more common, more sophisticated, and harder to detect. TeamPCP has shown they can repeatedly breach trusted systems, and they're getting better at hiding their tracks. ### Protecting Yourself from Similar Attacks So what can you do? First, don't panic. But do take action. Here are some practical steps: - Always verify package authenticity before installation - Use virtual environments to isolate dependencies - Implement regular security audits of your dependencies - Monitor for unusual network activity from development systems - Consider using additional security tools that scan for hidden payloads Remember, the goal isn't to be perfectly secure—that's impossible. The goal is to make yourself a harder target than the next developer. Most attackers will move on to easier prey if your defenses are even slightly better. ### The Bigger Picture of Supply Chain Security This incident with TeamPCP and the telnyx package isn't an isolated event. It's part of a growing trend where attackers target the tools developers trust most. They know that compromising one popular package can give them access to thousands of systems. We need to change how we think about security. It's not just about protecting our code—it's about protecting our entire development pipeline. From the packages we download to the repositories we trust, every link in the chain needs scrutiny. The good news? Awareness is growing. More developers are thinking about supply chain security, and tools are improving. But as TeamPCP has shown us, the attackers aren't standing still either. They're adapting, evolving, and finding new ways to hide their malicious code. Stay vigilant, verify your dependencies, and remember—sometimes the biggest threats come in the most unexpected packages.