Which versions of moonitoring are malicious?

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

How do I remediate moonitoring if I installed it?

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

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

Yes — moonitoring is associated with the RLMA-2025-01974, 2025-02-multis, RLUA-2026-00537 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 moonitoring 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 moonitoring (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 moonitoring across your stack and pipelines.

Malicious package

moonitoringPyPI

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

MAL-2025-2976

Immediate action

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

pip uninstall moonitoring

What this malware does

Infostealer with multiple possibilities, but not auto-activating on installation. There are already multiple attempts to publish it, with different innocent-looking names.

The campaign contains the with Infostealer itself and packages that include it as dependency and triggered.

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

Campaign: 2025-02-multis

Reasons (based on the campaign):

infostealer
The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

5cf94959543c0ca661727cd6f1d67305bba33fd454a49d4a72cbc01ffe010d21

eaae638b05e0294df1bfb545ddeb5e79fcbbd90414db984a394ef51d7f74b190

15670804eb18266dd9f95b15af455d0acc3b21b2f769ea608ea86b7265cf4326

aa4845284ef55bdee44f8609f4b960574fe72054e3458ffb4966371d2625a710

323a96cc1cc51c95934eacda075251001516b1fad56bbe36608dd59689c8e7bb

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 moonitoring (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 moonitoring across your stack and pipelines.
If you installed it — respond
moonitoring 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 moonitoring 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 moonitoring 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. moonitoring 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-019742025-02-multisRLUA-2026-00537

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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