Which versions of @b2bgeo/ci-aws are malicious?

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

How do I remediate @b2bgeo/ci-aws if I installed it?

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

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

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

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

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

Malicious package

@b2bgeo/ci-awsnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

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

MAL-2024-1979

Immediate action

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

npm uninstall @b2bgeo/ci-aws

Malicious versions

2 flagged

13.3.713.3.8

Indicators of compromise (SHA-256)

ebd5485ec543d10cf92825fa91aaba02f37c4212be8312acdbff68b4477878d2

26eb8709a1cbccce003f3919298a5e03e573e1a0c3c508c77e776cb206c9e146

ec9d58f44c64b08f91c51888ac52cf96d7b7cfa6bc50d5d5b9d6b33efe16bb2f

Detection & response playbook

Malicious package

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

References

security.snyk.io

Credits

ReversingLabs · finder

Detect & block this

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