Which versions of web3imports are malicious?

The following PyPI versions of web3imports are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate web3imports if I installed it?

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

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

Yes — web3imports is associated with the RLMA-2025-01258, 2025-01-asynchelpers, RLUA-2026-00918 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 web3imports 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 web3imports (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3imports across your stack and pipelines.

Malicious package

web3importsPyPI

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

MAL-2025-2012

Immediate action

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

pip uninstall web3imports

What this malware does

Importing the module starts (through init.py) the code that download, extracts and starts a remote executable. This has been identified by any.run as a AsyncRAT. The VirtusTotal detection rate was originally at the edge of false positive, but increased significantly during a few hours.

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

Campaign: 2025-01-asynchelpers

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

4596fb5c9e777f66263d34bbda6be30d81f63ff19a84b17bef39b688f6d70c55

5ea7b5e15abdc28f03e980217f5fc1fd3b6398c63e88a69300557d2d64ccfe96

84bb9be7600c163a4a67214f02bb476ce8498551fb0195bbe56161287d86c8cf

99b3b2bc5582277a557d1f3e8f547605c4f3a4f93fee23a0e83fdb815b960987

f48817572f00f6257470c77e8477ba54388fb446e58cb404f6feb992a30fa70a

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

Campaign

RLMA-2025-012582025-01-asynchelpersRLUA-2026-00918

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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