Telnyx Python SDK:供应链安全通知
Telnyx package compromised on PyPI

原始链接: https://telnyx.com/resources/telnyx-python-sdk-supply-chain-security-notice-march-2026

## Telnyx Python SDK 供应链攻击 - 2026年3月27日 2026年3月27日,恶意版本(4.87.1 & 4.87.2)的Telnyx Python SDK被短暂发布到PyPI,作为更广泛的供应链攻击的一部分,该攻击也影响了Trivy、Checkmarx和LiteLLM。这些受损版本包含恶意代码,具体利用了83.142.209.203:8080的C2服务器,并采用WAV隐写术进行有效载荷传递。 恶意软件包在~7小时内从PyPI上移除。**如果您在3月27日03:51-10:13 UTC之间安装或升级了`telnyx`软件包,或者没有固定版本,您可能受到影响。** **受影响的用户应立即降级到版本4.87.0或更早版本(`pip install telnyx==4.87.0`),并轮换所有密钥**(API密钥、数据库凭据等),这些密钥可以从受影响的环境中访问。 重要的是,Telnyx平台和API**没有**受到损害;此事件仅限于Python SDK的发布。 随着调查的进行,将发布进一步的入侵指标。 如需帮助,请联系[email protected]。

对不起。
## Telnyx PyPI 包被入侵 - 摘要 最近一起安全漏洞导致 Telnyx Python 包 (telnyx-python) 在 PyPI (Python 包索引) 上被入侵。受损版本包含恶意代码,旨在窃取数据,伪装成一个看似有效的音频文件。多个安全团队并行发现了这个问题,该包已被 PyPI 隔离。 该事件凸显了 Python 生态系统内持续存在的供应链漏洞。讨论的重点是如何改进安全措施,包括使用 `uv` 等工具,利用其排除最近发布的包的功能,以及推广标准化的、精选的包缓存(如 pip 26.1 将支持的)。 人们对 AI 生成代码日益带来的风险以及现代项目大量依赖项表示担忧。一些人认为,依赖于许多依赖项的项目本质上安全性较低。另一些人则提出了诸如 LLM 扫描的包镜像和更严格的发布控制(例如强制 2FA 用于包上传)等解决方案。该事件还引发了对 Telnyx 本身的安全实践以及替代 VoIP 提供商的讨论。
相关文章

原文

Summary

On March 27, 2026 at 03:51:28 UTC, two unauthorized versions of the Telnyx Python SDK were published to PyPI: versions 4.87.1 and 4.87.2. Both versions contained malicious code. Both were quarantined by 10:13 UTC the same day.

This incident is part of a broader supply chain campaign that has also affected Trivy, Checkmarx, and LiteLLM.

The Telnyx platform, APIs, and infrastructure were not compromised. This incident was limited to the PyPI distribution channel for the Python SDK.

Affected Versions

Version Published
telnyx==4.87.1 03:51:28 UTC, March 27, 2026
telnyx==4.87.2 Shortly after

Both versions have been removed from PyPI.

Who Is Affected

You may be affected if:

  • You installed or upgraded the telnyx Python package between 03:51 UTC and 10:13 UTC on March 27, 2026
  • You ran pip install telnyx without pinning a version and received 4.87.1 or 4.87.2
  • A dependency in your project pulled in telnyx as a transitive, unpinned dependency

Who Is NOT Affected

  • You are running version 4.87.0 or earlier
  • You did not install or upgrade the telnyx package between 03:51 UTC and 10:13 UTC on March 27
  • You are using the Telnyx REST API directly without the Python SDK

How to Check

Run the following command:

pip show telnyx                                                                                           
 

If the version shown is 4.87.1 or 4.87.2, treat the environment as compromised.

What to Do If Affected

  1. Downgrade immediately:
pip install telnyx==4.87.0                                                                                           
 
  1. Rotate all secrets accessible from the affected environment:
    • API keys
    • Database credentials
    • Cloud provider tokens
    • SSH keys
    • Any secrets stored in environment variables or configuration files
  2. Audit your systems for outbound connections to attacker infrastructure (see IOCs below)
  3. Review CI/CD pipelines and Docker builds that may have pulled the compromised version

Indicators of Compromise

Type Value
C2 server 83.142.209.203:8080
Exfil technique WAV steganography payload delivery

Additional IOCs will be published as the investigation confirms them.

What Was NOT Compromised

The Telnyx platform, voice services, messaging infrastructure, networking, SIP, AI inference, and all production APIs were not affected.

The SDK is a client library that wraps public APIs. It has no privileged access to Telnyx infrastructure. No customer data was accessed through this incident.

What We Are Doing

  • Malicious versions removed from PyPI
  • Investigating how publishing credentials were obtained

This attack is part of a multi-week supply chain campaign:

Questions?

Contact [email protected] if you have questions about this incident or need assistance determining if your environment was affected.

联系我们 contact @ memedata.com