Which versions of @b2bgeo/map-icons are malicious?

The following npm versions of @b2bgeo/map-icons are flagged malicious: 13.3.7. Treat any of these as compromised.

How do I remediate @b2bgeo/map-icons if I installed it?

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

If @b2bgeo/map-icons 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.

Is @b2bgeo/map-icons part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @b2bgeo/map-icons (version 13.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @b2bgeo/map-icons across your stack and pipelines.

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

Malicious package

@b2bgeo/map-iconsnpm

@b2bgeo/map-icons is a confirmed malicious npm package (MAL-2024-2650) that executes malicious code on install (malicious version 13.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @b2bgeo/map-icons (npm)

MAL-2024-2650

Immediate action

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

npm uninstall @b2bgeo/map-icons

Malicious versions

1 flagged

13.3.7

Indicators of compromise (SHA-256)

91e9240202814143ef99f25745e6aa82ea55775852b50451fcf4049d04cf3133

95ee6d2192cf0df316aaf665b37cda0ea2de813ff3eaa82ee19d2f65bf832501

f40f91f007b3e807d8d093d679f7ff08211308e218bb5a7dc1c17e16e16fa882

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @b2bgeo/map-icons (version 13.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @b2bgeo/map-icons across your stack and pipelines.
If you installed it — respond
Remove @b2bgeo/map-icons 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/map-icons 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.
How O3 protects you
O3 blocks @b2bgeo/map-icons 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/map-icons on npm has been identified as a malicious package (version 13.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00020RLUA-2024-05871

References

security.snyk.io

Credits

ReversingLabs · finder

Detect & block this

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