Which versions of eosio-signer are malicious?

The following PyPI versions of eosio-signer are flagged malicious: 0.0.1, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8. Treat any of these as compromised.

How do I remediate eosio-signer if I installed it?

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

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

Yes — eosio-signer is associated with the RLMA-2024-11032, 2024-11-eosio-signer, RLUA-2026-00297 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 eosio-signer 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 eosio-signer (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eosio-signer across your stack and pipelines.

Malicious package

eosio-signerPyPI

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

MAL-2024-11582

Immediate action

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

pip uninstall eosio-signer

What this malware does

Installing the package exfiltrates basic data about the system

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-eosio-signer

Reasons (based on the campaign):

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

Malicious versions

9 flagged

0.0.11.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.8

Indicators of compromise (SHA-256)

49b081a309f74fbc6bda456b2ec45d9a3a1e918f0473c5368b5c4181092a0b7b

a6251de30a6e6eeb2f67a5caef58223ebcdcf1a6113d45181830175ec4fbc3f2

647b75de784ff7b23edb8a5b76d1a017b02d1fd719c6a5a92587fa8d89c25abf

ca0b2c48f8c80d6ee0e3957aeeb1ab4e7361acd9f6bdf62cbc67ebfad6b10186

4e6eb69e6caddb6bb72ea6b04afba8aee8de66cc9293ef88d0cd6fe28a645491

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 eosio-signer (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eosio-signer across your stack and pipelines.
If you installed it — respond
eosio-signer 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 eosio-signer 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 eosio-signer 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. eosio-signer on PyPI has been identified as a malicious package (versions 0.0.1, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110322024-11-eosio-signerRLUA-2026-00297

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks eosio-signer-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