Supply chain · pip · High

Critical Malicious Package: 'platform-telemetry-client' in PyPI Ecosystem

Threat Engine Auto-Feed · data current as of 2026-09-12

A critical malicious package, 'platform-telemetry-client' version 1.0.0, has been identified in the PyPI ecosystem. This package is designed to establish persistence and download further payloads, posing a significant supply chain risk to Python environments.

  • Package: pip / platform-telemetry-client
  • Affected versions: = 1.0.0
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Malicious package

The 'platform-telemetry-client' package (version 1.0.0) contains malicious code that abuses Python's Path (PTH) file mechanism. This mechanism triggers a loader script every time Python initializes, which then attempts to download a next-stage payload. The payload is designed to be retrieved in chunks from DNS records, though the intended domain was not active during analysis.

How the attack works

This attack leverages a technique to achieve persistence within a Python environment. By modifying the Python path, a malicious script can be executed automatically upon interpreter initialization. This script then acts as a loader, attempting to fetch additional malicious components from external sources, often using covert channels like DNS for data exfiltration or command and control.

Who's exposed

Profiles most at risk

  • Development teams using Python (PyPI)
  • Organizations with CI/CD pipelines that pull Python dependencies
  • Any system or application that has installed 'platform-telemetry-client' version 1.0.0

Conditions that increase exposure

  • Unpinned dependencies allowing automatic updates to vulnerable versions
  • Lack of dependency lockfiles (e.g., requirements.txt.lock, poetry.lock) in production environments
  • Use of internal package mirrors that do not vet upstream packages
  • Automated build processes that do not scan new dependencies for known malicious indicators

Blast-radius scenarios

  • An attacker could gain persistent access to systems where the package is installed.
  • The loader could download and execute arbitrary code, leading to data exfiltration, system compromise, or further network penetration.
  • The blast radius includes any environment where Python is initialized after the malicious package is present, potentially affecting development, testing, and production systems.

What to do (defensive)

Detect

  • Scan dependency trees for 'platform-telemetry-client' version 1.0.0.
  • Monitor network traffic for suspicious DNS queries or connections to unknown domains from Python environments.
  • Inspect Python installation directories for unexpected .pth files or modifications to existing ones.
  • Utilize software composition analysis (SCA) tools to identify known malicious packages.

Contain

  • Isolate systems found to have installed 'platform-telemetry-client' version 1.0.0.
  • Block network egress from affected systems to prevent payload download and command-and-control communication.
  • Review and revoke credentials that may have been exposed on compromised systems.

Remediate

  • Immediately uninstall 'platform-telemetry-client' version 1.0.0 from all affected environments.
  • Perform a thorough audit of all Python dependencies to ensure no other malicious packages are present.
  • Rebuild affected environments from trusted sources, ensuring all dependencies are explicitly pinned to known-good versions.
  • Implement strict dependency management policies, including lockfiles and regular security scanning of all third-party components.

Frontier verdict — High

Prioritize immediate detection and removal of 'platform-telemetry-client' due to its critical severity and persistent payload delivery mechanism.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.