Telnyx has malicious code in PyPI versions 4.87.1 and 4.87.2
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI telnyx
- Affected
- >= 4.87.1, <= 4.87.2
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-955r-262c-33jc lists affected ranges: PyPI telnyx >=4.87.1 <=4.87.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-955r-262c-33jc lists affected ranges: PyPI telnyx >=4.87.1 <=4.87.2
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary On March 27, 2026, a threat actor used compromised PyPI credentials to publish malicious versions 4.87.1 and 4.87.2 of the telnyx Python package directly to PyPI. These versions contain credential-stealing malware and were not published through the legitimate GitHub release pipeline. Exposure Window | Version | Published (UTC) | Quarantined (UTC) | Exposure | |---------|-----------------|-------------------|----------| | 4.87.1 (broken) | 2026-03-27 03:51 | 2026-03-27 10:13 | 6h 22m | | 4.87.2 (functional) | 2026-03-27 04:07 | 2026-03-27 10:13 | 6h 6m | Both versions were quarantined by PyPI at 2026-03-27 10:13 UTC. Note: Version 4.87.1 contained a typo that prevented the malware from executing. Only 4.87.2 was fully functional. 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-955r-262c-33jc
- Revision 2 · amended ·
Amended from osv record GHSA-955r-262c-33jc
- Revision 1 · created ·
Published from ghsa record GHSA-955r-262c-33jc
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-955r-262c-33jc Advisory: Telnyx has malicious code in PyPI versions 4.87.1 and 4.87.2 IDs: GHSA-955r-262c-33jc Record: https://patchnext.com/advisories/ghsa-955r-262c-33jc (revision 3, source checked 26 Oct 2026, 13:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI telnyx: affected >= 4.87.1, <= 4.87.2 ## Suggested inspection (read-only) - `python -m pip show telnyx`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on telnyx. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-955r-262c-33jc (GitHub-reviewed advisory GHSA-955r-262c-33jc lists affected ranges: PyPI telnyx >=4.87.1 <=4.87.2) - Verified: https://osv.dev/vulnerability/GHSA-955r-262c-33jc (OSV record GHSA-955r-262c-33jc lists affected ranges: PyPI telnyx >=4.87.1 <=4.87.2) Commands are suggestions: review each one before running it.
Loading voting…