PYSEC-2026-3
Two telnyx versions published containing credential harvesting malware
After an API token exposure from an exploited Trivy dependency,
two new releases of telnyx were uploaded to PyPI containing automatically activated malware,
harvesting sensitive credentials and files, and exfiltrating to a remote API.
Compromised versions execute code during importing the telnyx module through modifications in _client.py.
The code downloads the next stages from endpoints on the host 83.142.209[.]203, encoded in WAV files.
On Windows hosts, the malicious executable is placed in
%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\msbuild.exe
for persistence and executed.
On other systems, the payload is a Python script.
After executing it, generated artifacts are exfiltrated to 83.142.209[.]203.
Version 4.87.1 contains a typo preventing the automated execution of the malicious code.
The code uses the encryption key observed in previous TeamPCP actions. The full compromise of exposed systems and all credentials reachable from them should be assumed. The credentials should be revoked/rotated, and the affected systems isolated and analyzed against malicious actions and modifications.
The two versions have been removed from PyPI, and the project has been reinstated.
What each source reports
OSV No score
Two telnyx versions published containing credential harvesting malware
After an API token exposure from an exploited Trivy dependency,
two new releases of telnyx were uploaded to PyPI containing automatically activated malware,
harvesting sensitive credentials and files, and exfiltrating to a remote API.
Compromised versions execute code during importing the telnyx module through modifications in _client.py.
The code downloads the next stages from endpoints on the host 83.142.209[.]203, encoded in WAV files.
On Windows hosts, the malicious executable is placed in
%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\msbuild.exe
for persistence and executed.
On other systems, the payload is a Python script.
After executing it, generated artifacts are exfiltrated to 83.142.209[.]203.
Version 4.87.1 contains a typo preventing the automated execution of the malicious code.
The code uses the encryption key observed in previous TeamPCP actions. The full compromise of exposed systems and all credentials reachable from them should be assumed. The credentials should be revoked/rotated, and the affected systems isolated and analyzed against malicious actions and modifications.
The two versions have been removed from PyPI, and the project has been reinstated.
- Record
PYSEC-2026-3- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
telnyxPyPI |
Listed versions 4.87.14.87.2 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
PYSEC-2026-3 is a vulnerability with no CVSS score yet in telnyx, published March 27, 2026. No source lists public exploit code. No source names a fixed version.
References
inspector.pypi.io/project/telnyx/4.87.2/packages/3c/89/bff9e644b1076b96ba1e23deb2b7acffa9fe84166219ba9cb47cf356b7ec/telnyx-4.87.2.tar.gz/telnyx-4.87.2/src/telnyx/_client.py
github.com/team-telnyx/telnyx-python/issues/235
endorlabs.com/learn/teampcp-strikes-again-telnyx-compromised-three-days-after-litellm
aikido.dev/blog/telnyx-pypi-compromised-teampcp-canisterworm