Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Compromised scope

@b2bgeo

The @b2bgeo scope on npm published 15 malicious packages. See the full package list, affected versions, and how to check whether your dependency tree pulled any of them in.

Malicious packages
15
Advisories
15
Ecosystem
npm
First seen
2024-06-25

What to do if you depend on any of these

Every package below was published as malicious under @b2bgeo. Treat any machine that installed one as compromised: remove the package and its lockfile entry, rotate every credential the build or runtime could reach (registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values) from a known-clean machine, and audit for unexpected outbound activity.

Because the packages share a publisher scope, a project that pulled in one has an elevated chance of having pulled in others. Search your lockfiles for @b2bgeo rather than checking a single package name.

All 15 packagesnpm