Which versions of anaconda-anon-usage are malicious?

The following PyPI versions of anaconda-anon-usage are flagged malicious: 0.4.9. Treat any of these as compromised.

How do I remediate anaconda-anon-usage if I installed it?

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

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

Yes — anaconda-anon-usage is associated with the RLMA-2024-07813, 2024-08-moti-analytics, RLUA-2026-00064 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 anaconda-anon-usage 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 anaconda-anon-usage (version 0.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging anaconda-anon-usage across your stack and pipelines.

Malicious package

anaconda-anon-usagePyPI

Malicious code in anaconda-anon-usage (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-9939

Immediate action

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

pip uninstall anaconda-anon-usage

What this malware does

The package is designed to exfiltrate basic data, like hostname and OS details, as well as collect information about the stacktrace it's imported from.

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-08-moti-analytics

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

1 flagged

0.4.9

Indicators of compromise (SHA-256)

7f15aa76dc7a25d78348920ecc166176ae7d8c650820a549101d0c992d280ff2

2461ce245ed1d160246d376e56cff9bb652e92d15f33484d553863493c6ca83b

681441a370f0819063d937bf24e1c9fdff7fd9dc5201da7e2c577d8a547fff51

13db314b26193e425dbdda1c92c17cfd11619d04857b6349801d0f7682b45336

40d0afbf0f97bb45365053a9f5328c9db40d68465e3227d9da01b05e774eaa99

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

Campaign

RLMA-2024-078132024-08-moti-analyticsRLUA-2026-00064

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks anaconda-anon-usage-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