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

scraper-npmPyPI

Malicious code in scraper-npm (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1000
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall scraper-npm

What this malware does

During import, the package exfiltrates files (especially .env and JSON) and eventually configures a backdoor by adding its own SSH key to the authorized_keys.

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

Campaign: 2026-02-scraper-npm

Reasons (based on the campaign):

  • files-exfiltration

  • backdoor

  • The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged
1.0.4

Indicators of compromise (SHA-256)

5705e85e8288aeffbfe964329624dcbb5b2e30cebb0023da5b605ee5fb0aef4e
d7f20e2472b63356859f93d837362f5473465c3bfe950dc41183d41aa2790d67

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 scraper-npm (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scraper-npm across your stack and pipelines.

  2. If you installed it — respond

    scraper-npm 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 scraper-npm 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 scraper-npm 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. scraper-npm on PyPI has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-scraper-npm

References

Credits

  • Kamil Mańkowski (kam193) · analyst

Detect & block this

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

scraper-npm (PyPI) malicious package — MAL-2026-1000 | O3 Security