Which versions of @b2b-portal/form are malicious?

The following npm versions of @b2b-portal/form are flagged malicious: 4.1.8. Treat any of these as compromised.

How do I remediate @b2b-portal/form if I installed it?

Remove @b2b-portal/form 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 @b2b-portal/form — how do I know if it already compromised me?

If @b2b-portal/form 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 @b2b-portal/form part of a known attack campaign?

Yes — @b2b-portal/form is associated with the GHSA-7rrw-hm44-329g 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 @b2b-portal/form 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 @b2b-portal/form (version 4.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @b2b-portal/form across your stack and pipelines.

Malicious package

@b2b-portal/formnpm

Malicious code in @b2b-portal/form (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2537

Immediate action

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

npm uninstall @b2b-portal/form

What this malware does

The package @b2b-portal/form 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 '@b2b-portal/form' @ 4.1.8 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

4.1.8

Indicators of compromise (SHA-256)

02ca26818fe477e83ab1790e1bb62bd6445af229108210e4f0409dc644423de4

7bfd3d2bf611173cd9899eb7ae28620ce52dd78812b47d5f9ca1fc68555c5b70

01b5517a25cba37fda750436dbbba1fe86b2c36fb7eafbbb0b49cf17d95e5a27

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

Campaign

GHSA-7rrw-hm44-329g

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @b2b-portal/form-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