Which versions of no-unsanitized are malicious?

The following npm versions of no-unsanitized are flagged malicious: 9.9.1, 9.9.2. Treat any of these as compromised.

How do I remediate no-unsanitized if I installed it?

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

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

Yes — no-unsanitized is associated with the RLMA-2025-06403 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 no-unsanitized across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for no-unsanitized (2 malicious versions).

Malicious package

no-unsanitizednpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

no-unsanitized is a confirmed malicious npm package (MAL-2025-192824) that executes malicious code on install (malicious versions 9.9.1, 9.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in no-unsanitized (npm)

MAL-2025-192824

Immediate action

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

npm uninstall no-unsanitized

What this malware does

The package no-unsanitized was found to contain malicious code.

Malicious versions

2 flagged

9.9.19.9.2

Indicators of compromise (SHA-256)

0f75b9f74bea833b2881301654c6fc200a27cf7d9bc57bdbfe673efe625fb30d

2d6c1464dc8a69f1cb4ee6d3ef31f42233b9cde5eeb84fe01562b5f0e43b3ab4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06403

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks no-unsanitized-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