Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @b2bgeo published 15 malicious packages. See the full campaign →
Malicious package

@b2bgeo/frontend-server-api-typesnpm

@b2bgeo/frontend-server-api-types is a confirmed malicious npm package (MAL-2024-2395) 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/frontend-server-api-types (npm)

MAL-2024-2395
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @b2bgeo/frontend-server-api-types

Malicious versions

2 flagged
13.3.713.3.8

Indicators of compromise (SHA-256)

c35cd732266fe110eb41bcd16ddde069c39908afce51a860d52461cfa32fa8dc
5902ac47cd368a6f602ad92c1fb2533239aa6421c673de0fd3299dbd43be0a94
da364804d516142fedd7237f53d2369ea5ed31a717186d65ca274b272798d1c0

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @b2bgeo/frontend-server-api-types (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/frontend-server-api-types across your stack and pipelines.

  2. If you installed it — respond

    Remove @b2bgeo/frontend-server-api-types 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.

  3. Did it already run?

    If @b2bgeo/frontend-server-api-types 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.

  4. How O3 protects you

    O3 blocks @b2bgeo/frontend-server-api-types 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/frontend-server-api-types 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-00019RLUA-2024-05870

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @b2bgeo/frontend-server-api-types-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
@b2bgeo/frontend-server-api-types (npm) malicious package — MAL-2024-2395 | O3 Security