Which versions of web3author are malicious?

The following PyPI versions of web3author are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate web3author if I installed it?

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

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

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

Malicious package

web3authorPyPI

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

MAL-2025-4269

Immediate action

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

pip uninstall web3author

What this malware does

Package contains just a function to send out data. It (or a package sharing the same IoCs) is used in a malicious GitHub project to exfiltrate crypto currency private keys, e.g. https://github.com/taikoyaki/MegaEth-Auto-Bot/blob/772b4591daaa0b200d1bd1fd3be3d48b8433f084/cap/cap.py#L49

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

Campaign: 2025-04-alchemyrpcs

Reasons (based on the campaign):

crypto-related
The malicious code is intentionally included in a dependency of the package
exfiltration-crypto

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a0b36f5e65a090983db0db0e90790e0b5c2b8173cfb1d641028544003d053819

89f9e349e967d4972e6666e7fbe09bb4ceefa8ff19955964a6526cffe506eac6

d5eac126109d648cac7a74217f0bc4b9e9bd0d07dc400924bf346f90b4b7ad9d

3bee664c9376b517cfb9fe199dad3ee71e3dd60bc0d2979659b810b1620f7ce8

b4c722de6ab72214abf8022f6241c4385459009616c0bbe54457b28cb180bdfa

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

Campaign

RLMA-2025-026272025-04-alchemyrpcsRLUA-2026-00915

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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