Which versions of safeness-sb-new are malicious?

The following npm versions of safeness-sb-new are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate safeness-sb-new if I installed it?

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

If safeness-sb-new 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 safeness-sb-new part of a known attack campaign?

Yes — safeness-sb-new is associated with the RLMA-2026-01544 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 safeness-sb-new across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for safeness-sb-new (version 0.0.2).

Malicious package

safeness-sb-newnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

safeness-sb-new is a confirmed malicious npm package (MAL-2026-1841) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in safeness-sb-new (npm)

MAL-2026-1841

Immediate action

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

npm uninstall safeness-sb-new

What this malware does

The package safeness-sb-new was found to contain malicious code.

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

90ac406a17ae04bbc6840219acaed5daacbfa1b35ece6f6f704fd3d8b6b0fd10

9766c02e9c5a79f96104b5089c06ae16b472ff7734284462bd3bfe0fe3c4a687

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01544

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks safeness-sb-new-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