Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Two telnyx versions published containing credential harvesting malware

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.

Add to your agent

Affected packages

  • PyPI telnyx

    Affected
    >= 4.87.1, <= 4.87.1>= 4.87.2, <= 4.87.2
    Fixed in
    no fixed version recorded

Sources

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.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record PYSEC-2026-3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: pysec-2026-3

Advisory: Two telnyx versions published containing credential harvesting malware
IDs: pysec-2026-3
Record: https://patchnext.com/advisories/pysec-2026-3 (revision 1, source checked 24 Oct 2026, 04:13 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.1; >= 4.87.2, <= 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://osv.dev/vulnerability/PYSEC-2026-3 (OSV record PYSEC-2026-3 lists affected ranges: PyPI telnyx >=4.87.1 =4.87.2 <=4.87.2)

Commands are suggestions: review each one before running it.

Loading voting…