Which versions of wiz-dev are malicious?

The following npm versions of wiz-dev are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate wiz-dev if I installed it?

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

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

Yes — wiz-dev is associated with the RLMA-2026-01648 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 wiz-dev across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wiz-dev (2 malicious versions).

Malicious package

wiz-devnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

wiz-dev is a confirmed malicious npm package (MAL-2026-1874) that executes malicious code on install (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wiz-dev (npm)

MAL-2026-1874

Immediate action

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

npm uninstall wiz-dev

What this malware does

The package wiz-dev was found to contain malicious code.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

db4d034ff5b8ccb9e626c2ced53c5f2be7ed503ef4bdabef77f1c64702a95e40

be8c0c61ad6d8e5e76edbce5a6e053676767ed4dcabed1c20389db704cc20411

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wiz-dev (2 malicious versions).
If you installed it — respond
Remove wiz-dev 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 wiz-dev 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. wiz-dev on npm has been identified as a malicious package (versions 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01648

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks wiz-dev-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