Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

system-health-check-test-uniquePyPI

Malicious code in system-health-check-test-unique (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192679
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall system-health-check-test-unique

What this malware does

Importing the module exfiltrates content of /var/www/html to a remote host

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

Campaign: 2025-12-system-health-check-test-unique

Reasons (based on the campaign):

  • files-exfiltration

  • obfuscation

Malicious versions

13 flagged
0.1.50.1.60.2.60.2.70.2.80.2.90.3.00.3.10.3.20.3.30.3.40.3.50.3.6

Indicators of compromise (SHA-256)

10bfd6e986187675dd7d7e3a8f860807e408fd6a91694ca0e0128be83fa8fc47
5ea3f538083de70d12dc155af48cf0a23c0ed2803cac97b5dbf093265a71558d
439ce225263440aa80bc75e3ae0bbf2b290e849a05368cc8eb0bfcd380c7177a

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for system-health-check-test-unique (13 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging system-health-check-test-unique across your stack and pipelines.

  2. If you installed it — respond

    system-health-check-test-unique 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.

  3. Did it already run?

    If system-health-check-test-unique 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.

  4. How O3 protects you

    O3 blocks system-health-check-test-unique 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. system-health-check-test-unique on PyPI has been identified as a malicious package (versions 0.1.5, 0.1.6, 0.2.6, 0.2.7, 0.2.8, 0.2.9, 0.3.0, 0.3.1, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-system-health-check-test-unique

References

Credits

  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks system-health-check-test-unique-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
system-health-check-test-unique (PyPI) malicious package — MAL-2025-192679 | O3 Security