What does the bizsignupnodeweb malware do?

The package bizsignupnodeweb was found to contain malicious code. The OpenSSF Package Analysis project identified 'bizsignupnodeweb' @ 99.11.9 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of bizsignupnodeweb are malicious?

The following npm versions of bizsignupnodeweb are flagged malicious: 99.11.9. Treat any of these as compromised.

How do I remediate bizsignupnodeweb if I installed it?

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

If bizsignupnodeweb 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 bizsignupnodeweb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bizsignupnodeweb (version 99.11.9).

Malicious package

bizsignupnodewebnpm

Advisory published Mar 29, 2026Updated Mar 31, 2026

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

Malicious code in bizsignupnodeweb (npm)

MAL-2026-2284

Immediate action

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

npm uninstall bizsignupnodeweb

What this malware does

The package bizsignupnodeweb was found to contain malicious code.

The OpenSSF Package Analysis project identified 'bizsignupnodeweb' @ 99.11.9 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.11.9

Indicators of compromise (SHA-256)

db21d1edf6c7a5e050edd0345bd644bb382ab3fc3098d3ec5c1be1ed26761739

ceaf1cee13e367f987a97f8de4c8fb4985ab1eedd49be1912467793dce9f0ef9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bizsignupnodeweb (version 99.11.9).
If you installed it — respond
Remove bizsignupnodeweb 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 bizsignupnodeweb 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. bizsignupnodeweb on npm has been identified as a malicious package (version 99.11.9 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 bizsignupnodeweb-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