Which versions of node-business are malicious?

The following npm versions of node-business are flagged malicious: 5.3.18, 5.5.20, 5.5.21, 5.5.22, 5.5.23. Treat any of these as compromised.

How do I remediate node-business if I installed it?

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

If node-business was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is node-business part of a known attack campaign?

Yes — node-business is associated with the GHSA-2prc-m9c3-jgwp, RLMA-2026-01796, RLUA-2026-02001 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 node-business across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-business (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-business across your stack and pipelines.

Malicious package

node-businessnpm

Malicious code in node-business (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1959

Immediate action

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

npm uninstall node-business

What this malware does

The package node-business was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

5 flagged

5.3.185.5.205.5.215.5.225.5.23

Indicators of compromise (SHA-256)

056b764f3a3ce19cb19eb194a6a00e7ee3e1fb99de205cb4dc27870b8c6721aa

792eac8bec173409a594f162c30deb42b1fd0592892e4c5aa5884cab16290b90

e3d6692608c9a6f64113fe356fed71d65db1e15cae89c6fa23fc811e840a7eaf

6f26fdc4f7891c40c33f83acfa6c46036b668dead717cd7d32bb386a9fac54f4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-business (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-business across your stack and pipelines.
If you installed it — respond
Remove node-business 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 node-business was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks node-business before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. node-business on npm has been identified as a malicious package (versions 5.3.18, 5.5.20, 5.5.21, 5.5.22, 5.5.23 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2prc-m9c3-jgwpRLMA-2026-01796RLUA-2026-02001

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-business-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