Which versions of hope-mapboxdraw are malicious?

The following npm versions of hope-mapboxdraw are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate hope-mapboxdraw if I installed it?

hope-mapboxdraw is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed hope-mapboxdraw — how do I know if it already compromised me?

If hope-mapboxdraw 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 hope-mapboxdraw part of a known attack campaign?

Yes — hope-mapboxdraw is associated with the GHSA-x6p5-q554-49mq 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 hope-mapboxdraw 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 hope-mapboxdraw (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hope-mapboxdraw across your stack and pipelines.

Malicious package

hope-mapboxdrawnpm

Malicious code in hope-mapboxdraw (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190963

Immediate action

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

npm uninstall hope-mapboxdraw

What this malware does

The package hope-mapboxdraw was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

b7e22015802e90e30eb1ecbc96b04e60f72c743f0a41567bbf6259b9b375afb3

6df66ea17d715faf27f78cc71434fc12bea5684441bf51f652b2ab98a8eb2787

53b56bcb1f123270a333f6241f8934f0740d2c9b33c99c367604f067fc6faf9c

270f9a1d1a6ff84ce768a14ecdb1b08fafb80a6e55f2c985c3a9df05cc1bfd78

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hope-mapboxdraw (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hope-mapboxdraw across your stack and pipelines.
If you installed it — respond
hope-mapboxdraw is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If hope-mapboxdraw 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 hope-mapboxdraw 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. hope-mapboxdraw on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x6p5-q554-49mq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hope-mapboxdraw-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring