Which versions of @abdulmz/mz-test are malicious?

The following npm versions of @abdulmz/mz-test are flagged malicious: 1.1.1. Treat any of these as compromised.

How do I remediate @abdulmz/mz-test if I installed it?

Remove @abdulmz/mz-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @abdulmz/mz-test — how do I know if it already compromised me?

If @abdulmz/mz-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @abdulmz/mz-test part of a known attack campaign?

Yes — @abdulmz/mz-test is associated with the RLMA-2024-00003, RLUA-2024-05855, RLUA-2026-05789 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 @abdulmz/mz-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @abdulmz/mz-test (version 1.1.1).

Malicious package

@abdulmz/mz-testnpm

Advisory published Jun 25, 2024Updated Sep 1, 2026

@abdulmz/mz-test is a confirmed malicious npm package (MAL-2024-2688) that executes malicious code on install (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @abdulmz/mz-test (npm)

MAL-2024-2688

Immediate action

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

npm uninstall @abdulmz/mz-test

Malicious versions

1 flagged

1.1.1

Indicators of compromise (SHA-256)

36eb175c6f6e16fbc779fd43dddb8878867359ea58e6334d93916d61517713b3

9966fbb6889e686dbe3f9caa4e12bd176a830e940a0d98399d4afc9182360f15

dd83a41bd019f74bc984a22b862fb849c10f1baafad5101219bf6cd1493bb174

16c88d73e559d8814e98671440942d601174ddcd99579bed00d64c6f17d0ebc9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @abdulmz/mz-test (version 1.1.1).
If you installed it — respond
Remove @abdulmz/mz-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @abdulmz/mz-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @abdulmz/mz-test on npm has been identified as a malicious package (version 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00003RLUA-2024-05855RLUA-2026-05789

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @abdulmz/mz-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database