Which versions of platform-telemetry-client are malicious?

The following PyPI versions of platform-telemetry-client are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate platform-telemetry-client if I installed it?

platform-telemetry-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed platform-telemetry-client — how do I know if it already compromised me?

If platform-telemetry-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is platform-telemetry-client part of a known attack campaign?

Yes — platform-telemetry-client is associated with the 2026-09-platform-telemetry-client campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find platform-telemetry-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for platform-telemetry-client (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging platform-telemetry-client across your stack and pipelines.

Malicious package

platform-telemetry-clientPyPI

platform-telemetry-client is a confirmed malicious PyPI package (MAL-2026-16141) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in platform-telemetry-client (PyPI)

MAL-2026-16141

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall platform-telemetry-client

What this malware does

The package contains PTH file triggering the loader on every Python initialization. The loader tries to download next stage payload stored in chunks in DNS records. During analysis, the intended domain was not yet registered. The chosen name suggests relation to the campaign 2026-09-openaii.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-09-platform-telemetry-client

Reasons (based on the campaign):

abuses-pth
data-stored-in-dns
obfuscation

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7464733f1d7353ae3aa3c9da2c60116c92298bfd84c94a6cba4e5f423cb0a0eb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for platform-telemetry-client (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging platform-telemetry-client across your stack and pipelines.
If you installed it — respond
platform-telemetry-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If platform-telemetry-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks platform-telemetry-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. platform-telemetry-client on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-platform-telemetry-client

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks platform-telemetry-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database