Which versions of @b2bgeo/tanker are malicious?

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

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

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

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

Yes — @b2bgeo/tanker is associated with the RLMA-2024-00023, RLUA-2024-05874 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/tanker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @b2bgeo/tanker (2 malicious versions).

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

Malicious package

@b2bgeo/tankernpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

@b2bgeo/tanker is a confirmed malicious npm package (MAL-2024-3079) 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/tanker (npm)

MAL-2024-3079

Immediate action

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

npm uninstall @b2bgeo/tanker

Malicious versions

2 flagged

13.3.713.3.8

Indicators of compromise (SHA-256)

c6df285c75a7e097508efec541667f840ad831e847aa64ff67c37bd324039591

023660573133ccfd7962a2dbff4125489fd82778489fe74b12fdedb5a418b987

d1d53080484c3897c616331f4901d52f8f029e3760f30f107d444b009907de5e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @b2bgeo/tanker (2 malicious versions).
If you installed it — respond
Remove @b2bgeo/tanker 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/tanker 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/tanker 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-00023RLUA-2024-05874

References

security.snyk.io

Credits

ReversingLabs · finder

Detect & block this

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