Which versions of elbloadmonitor are malicious?

The following PyPI versions of elbloadmonitor are flagged malicious: 0.0.1, 0.1.12. Treat any of these as compromised.

How do I remediate elbloadmonitor if I installed it?

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

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

Yes — elbloadmonitor is associated with the RLMA-2025-03590, GENERIC-standard-pypi-install-pentest, RLUA-2026-00290 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 elbloadmonitor 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 elbloadmonitor (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging elbloadmonitor across your stack and pipelines.

Malicious package

elbloadmonitorPyPI

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

MAL-2025-6499

Immediate action

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

pip uninstall elbloadmonitor

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

0.0.10.1.12

Indicators of compromise (SHA-256)

c6043ad06799853c63a89e3fd4a43dc8dda5a9fda15302a15db69c2fb5d277e4

918af17da12c4aaeb062c0fa53f51ccd8f7ba0abf65fbfafc35e1e1e65cdef60

88c42654181376acf7c6b7f01d62ff8c47962c3405e54d1924caa9de70e01548

9375172952f24589dd79eebd159fca9b1419db21ed09ff90355b6485dcb6ba74

2507d38051c0138314e9f490fc28ca622de982cd583d67acf0cfc11917ef64a3

d780dd1580b04693beebf9a786fe076da608c10ddca1e3cfdeaa9df378bbe7e3

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

Campaign

RLMA-2025-03590GENERIC-standard-pypi-install-pentestRLUA-2026-00290

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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