Which versions of platforms are malicious?

The following PyPI versions of platforms are flagged malicious: 1.0.0, 1.0.1, 2.0.0, 3.0.0, 4.0.0, 5.0.0, 6.0.0. Treat any of these as compromised.

How do I remediate platforms if I installed it?

platforms 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 platforms — how do I know if it already compromised me?

If platforms 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 platforms part of a known attack campaign?

Yes — platforms is associated with the 2026-02-old-platforms 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 platforms 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 platforms (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging platforms across your stack and pipelines.

Malicious package

platformsPyPI

Malicious code in platforms (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-901

Immediate action

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

pip uninstall platforms

What this malware does

During importing, the code automatically starts a Telegram bot designed to download and save files locally upon a specific message in the channel. While this seems to have limited harm, this behavior is not disclosed and involved packages have typosquatting-like names. The core code is in the "platforms" package

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

Campaign: 2026-02-old-platforms

Reasons (based on the campaign):

other
typosquatting
The malicious code is intentionally included in a dependency of the package

Malicious versions

7 flagged

1.0.01.0.12.0.03.0.04.0.05.0.06.0.0

Indicators of compromise (SHA-256)

152f27ebcd7a8c662ffcbfe69086e0a50e71f73993bc7d97ce3bb67896c8a4dc

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 platforms (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging platforms across your stack and pipelines.
If you installed it — respond
platforms 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 platforms 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 platforms 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. platforms on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 2.0.0, 3.0.0, 4.0.0, 5.0.0, 6.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-old-platforms

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks platforms-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