Which versions of oz-merkle-tree are malicious?

The following PyPI versions of oz-merkle-tree are flagged malicious: 0.1.8. Treat any of these as compromised.

How do I remediate oz-merkle-tree if I installed it?

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

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

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

Malicious package

oz-merkle-treePyPI

Malicious code in oz-merkle-tree (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10100

Immediate action

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

pip uninstall oz-merkle-tree

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.1.8

Indicators of compromise (SHA-256)

43f9fc635e80946508e8cd2894670bf3a9c2274f2da129fe0ee77d83745b8750

f5936e41d9cf736df16d8930a8b8c8a53aca7a05270f6b0ed89d6d2047bef050

732a4768703da4c9eb31465258c2df9b93dcfcf2811b78c72b62d9dbf9b10053

5d4d5ddbf70cbc594f06c13774b6ee92999de200ce96435e4d1dd919a6f13138

e1c801d1e2f46314e7f45fa6586183fc7e92ada55459de4f23d93404fa8b4f1c

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

Campaign

RLMA-2024-086462024-08-moti-analyticsRLUA-2026-00577

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks oz-merkle-tree-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