Which versions of b2bneo-rest are malicious?

The following npm versions of b2bneo-rest are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate b2bneo-rest if I installed it?

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

If b2bneo-rest 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.

How do I find b2bneo-rest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for b2bneo-rest (version 1.0.2).

Malicious package

b2bneo-restnpm

Advisory published May 6, 2026Updated May 12, 2026

b2bneo-rest is a confirmed malicious npm package (MAL-2026-3359) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in b2bneo-rest (npm)

MAL-2026-3359

Immediate action

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

npm uninstall b2bneo-rest

What this malware does

The package b2bneo-rest was found to contain malicious code.

The OpenSSF Package Analysis project identified 'b2bneo-rest' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

cf1119509e8be536b85c815e989985be52710522dc2dc769732f60a7c55202a7

81aa2ce0b474a6829ca4aa8dca5776be81b750b88d093c610de24760671b8fb6

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks b2bneo-rest-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