Which versions of @b2bgeo/certs are malicious?

The following npm versions of @b2bgeo/certs are flagged malicious: 13.3.7, 13.3.8. Treat any of these as compromised.

How do I remediate @b2bgeo/certs if I installed it?

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

If @b2bgeo/certs 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 @b2bgeo/certs part of a known attack campaign?

Yes — @b2bgeo/certs is associated with the RLMA-2024-00012, RLUA-2024-05863 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 @b2bgeo/certs 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 @b2bgeo/certs (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @b2bgeo/certs across your stack and pipelines.

Part of a larger attack: @b2bgeo published 15 malicious packages. See the full campaign →

Malicious package

@b2bgeo/certsnpm

@b2bgeo/certs is a confirmed malicious npm package (MAL-2024-1971) that executes malicious code on install (malicious versions 13.3.7, 13.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @b2bgeo/certs (npm)

MAL-2024-1971

Immediate action

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

npm uninstall @b2bgeo/certs

Malicious versions

2 flagged

13.3.713.3.8

Indicators of compromise (SHA-256)

26e88e80235d4cf1083700cc0eb362d2b4d18fc135e65962afb576e750256eab

902b4a71d79cb2a414d93ffdd8fdd1296680871fd0c497b05f4b17e1a73647ac

f2cd785cde5a0f330e4fd4dff9a7e118459fb84891eb9ad33262d82b7f7c5ea8

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

Campaign

RLMA-2024-00012RLUA-2024-05863

References

security.snyk.io

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @b2bgeo/certs-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