Which versions of bubblemap-bypass-sdk are malicious?

Every published version of bubblemap-bypass-sdk on npm is considered malicious. Remove the package entirely.

How do I remediate bubblemap-bypass-sdk if I installed it?

Remove bubblemap-bypass-sdk 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 bubblemap-bypass-sdk — how do I know if it already compromised me?

If bubblemap-bypass-sdk 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 bubblemap-bypass-sdk part of a known attack campaign?

Yes — bubblemap-bypass-sdk is associated with the GHSA-v36r-mccr-r29h 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 bubblemap-bypass-sdk 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 bubblemap-bypass-sdk (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bubblemap-bypass-sdk across your stack and pipelines.

Malicious package

bubblemap-bypass-sdknpm

Malicious code in bubblemap-bypass-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1190

Immediate action

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

npm uninstall bubblemap-bypass-sdk

What this malware does

The package bubblemap-bypass-sdk 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

7a3f00a5bb4b17e14ecf7551be614e21a76a0c92c1b351b0b995f9df4bf128ba

d18639f5df9977e99869d513c7daa36c9a83720ceaf920d117ae64b4e50a16eb

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

Campaign

GHSA-v36r-mccr-r29h

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bubblemap-bypass-sdk-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