Which versions of @b2bgeo/backend-api-types are malicious?

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

How do I remediate @b2bgeo/backend-api-types if I installed it?

Remove @b2bgeo/backend-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.

I already installed @b2bgeo/backend-api-types — how do I know if it already compromised me?

If @b2bgeo/backend-api-types was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @b2bgeo/backend-api-types part of a known attack campaign?

Yes — @b2bgeo/backend-api-types is associated with the RLMA-2024-00011, RLUA-2024-05862 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/backend-api-types across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @b2bgeo/backend-api-types (2 malicious versions).

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

Malicious package

@b2bgeo/backend-api-typesnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

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

MAL-2024-1806

Immediate action

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

npm uninstall @b2bgeo/backend-api-types

Malicious versions

2 flagged

13.3.713.3.8

Indicators of compromise (SHA-256)

c82c53f178a067128e902a51577d0f30d3f34999fb241d98e08d979853614f50

12bffe2d28fdffa4ca9dbad29803428ccce35b199fb7b9a57bbb9413f1ff8ee9

a6a647e1ea2b6cbc9f84297f11ecfa6d14bb7e639c99e3ae3f5c35663070f105

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @b2bgeo/backend-api-types (2 malicious versions).
If you installed it — respond
Remove @b2bgeo/backend-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.
Did it already run?
If @b2bgeo/backend-api-types was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @b2bgeo/backend-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-00011RLUA-2024-05862

References

security.snyk.io

Credits

ReversingLabs · finder

Detect & block this

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