Which versions of mapbox-gl-ts are malicious?

The following npm versions of mapbox-gl-ts are flagged malicious: 10.0.1. Treat any of these as compromised.

How do I remediate mapbox-gl-ts if I installed it?

Remove mapbox-gl-ts 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 mapbox-gl-ts — how do I know if it already compromised me?

If mapbox-gl-ts 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 mapbox-gl-ts part of a known attack campaign?

Yes — mapbox-gl-ts is associated with the GHSA-9xgr-9vpq-9j9f, RLMA-2025-05424, RLUA-2025-05884 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 mapbox-gl-ts 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 mapbox-gl-ts (version 10.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mapbox-gl-ts across your stack and pipelines.

Malicious package

mapbox-gl-tsnpm

mapbox-gl-ts is a confirmed malicious npm package (MAL-2025-47998) that executes malicious code on install (malicious version 10.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mapbox-gl-ts (npm)

MAL-2025-47998

Immediate action

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

npm uninstall mapbox-gl-ts

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

10.0.1

Indicators of compromise (SHA-256)

8d036b317c8c49cc8982dedb6417e57b1669e9dfc07159bf4a7e6fb136ff939c

825ee63dc46b51eb37503f0830ac65038099c40ec7feefc7cebe84742d573d06

85d05d47ff9339a9f66b6d0a2ed9305710c37bd9f975ed9023bd0ad4d496b257

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 mapbox-gl-ts (version 10.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mapbox-gl-ts across your stack and pipelines.
If you installed it — respond
Remove mapbox-gl-ts 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 mapbox-gl-ts 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 mapbox-gl-ts 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. mapbox-gl-ts on npm has been identified as a malicious package (version 10.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9xgr-9vpq-9j9fRLMA-2025-05424RLUA-2025-05884

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks mapbox-gl-ts-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