Which versions of gbiz-next are malicious?

The following npm versions of gbiz-next are flagged malicious: 2.3.19. Treat any of these as compromised.

How do I remediate gbiz-next if I installed it?

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

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

Yes — gbiz-next is associated with the GHSA-rfgw-mj8j-mg3g 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 gbiz-next 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 gbiz-next (version 2.3.19). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gbiz-next across your stack and pipelines.

Malicious package

gbiz-nextnpm

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

MAL-2025-190573

Immediate action

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

npm uninstall gbiz-next

What this malware does

The package gbiz-next 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.

The OpenSSF Package Analysis project identified 'gbiz-next' @ 2.3.19 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

2.3.19

Indicators of compromise (SHA-256)

8e435f85a2ff89a4babb89f2e0bb7bfbf3ff40d1e4e7b4d531fed1c4b74e7343

553cbc6a459ec9d1b6f955fcef3ae6eb80c745689510710611df3d9d6527c2fd

c8391a7e1c2a64a130ced055b9f21e596e7bde4ba799add2094c42c4bf63613b

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 gbiz-next (version 2.3.19). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gbiz-next across your stack and pipelines.
If you installed it — respond
Remove gbiz-next 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 gbiz-next 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 gbiz-next 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. gbiz-next on npm has been identified as a malicious package (version 2.3.19 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rfgw-mj8j-mg3g

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks gbiz-next-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