Which versions of websign are malicious?

The following PyPI versions of websign are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate websign if I installed it?

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

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

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

Malicious package

websignPyPI

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

MAL-2025-4273

Immediate action

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

pip uninstall websign

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

0.1.0

Indicators of compromise (SHA-256)

4a59dc6694a22280d53c39ce67f7230e3ebda36804168fcb82211273e324d878

6505d88c061e297b18178a440c9d55729c873a37a57a09115befe1fb6eb2a22e

25ea98e45fc0e99bfc731d77e2205bd14c901fc33ba6b8639b441b97739db0e2

1c2cd23b18ab4866022a4e611707833e084f18086971595f873b40013905455b

7b3df3514dc1c53965225b35305ca024f87fd90d1481ec4698f8023330d10283

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

Campaign

RLMA-2025-026312025-04-alchemyrpcsRLUA-2026-00925

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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