Which versions of scrapetools2 are malicious?

The following PyPI versions of scrapetools2 are flagged malicious: 0.2.0, 0.2.1, 1.2.0, 1.2.1. Treat any of these as compromised.

How do I remediate scrapetools2 if I installed it?

Remove scrapetools2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed scrapetools2 — how do I know if it already compromised me?

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

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

Malicious package

scrapetools2PyPI

scrapetools2 is a confirmed malicious PyPI package (MAL-2026-17199) that executes malicious code on install (malicious versions 0.2.0, 0.2.1, 1.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in scrapetools2 (PyPI)

MAL-2026-17199

Immediate action

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

pip uninstall scrapetools2

What this malware does

scrapetools2 1.2.1 ships an auto-update mechanism in downloader.py that fetches tar.gz payloads from public IPFS gateways (eu.orbitor.dev, dget.top, ipfs.filebase.io) at the author-controlled IPNS name k51qzi5uqu5dmh5178x8jzdkz8u3k3qona4zrwlvdr6865it3901l1oe8emjwc, decrypts an 'updates' entry using a Fernet key bundled inside the package (scrapetools2/versions), writes each decrypted blob to scrapetools2/modules/N.py, and then compile()+exec()s them in-process. The updater is invoked via runtime.DBConsumer.startQueue -> updater() and loops on a 60-second interval, so any code path that reaches the advertised RuntimeSite/browser-pool flow triggers the fetch-and-execute cycle. The package additionally ships an encrypted 'updates' blob decrypted by packer.unpackdata into a JSON {"cmd":...} whose contents are written to modules/*.py and exec'd by run_modules(); the executed source is not visible in the sdist without the bundled key. Because IPNS is a mutable pointer under the holder's control and the only integrity check is a Fernet key shipped with the package, whoever controls the IPNS name can push arbitrary Python that will be executed on installer hosts.

Malicious versions

4 flagged

0.2.00.2.11.2.01.2.1

Indicators of compromise (SHA-256)

44124d389269a5e4dc8801d3af1afeb08aee57313fcc7082570c5890e7d89233

8510a108179eb7e480d606cb4f037c1365007926af575afc80ec0d9f077f1b0a

cf460a24ad3c20f436eb20e2974b090ae761ebb02e170d92c34aadf23b320007

d1ccba931f3617a01ef93e1f81268e9cd3cc74645566804cb1ab64e53f6ded64

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for scrapetools2 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scrapetools2 across your stack and pipelines.
If you installed it — respond
Remove scrapetools2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If scrapetools2 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 scrapetools2 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. scrapetools2 on PyPI has been identified as a malicious package (versions 0.2.0, 0.2.1, 1.2.0, 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020574IN-MAL-2026-020575IN-MAL-2026-020576IN-MAL-2026-020577

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks scrapetools2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database