Which versions of bubblestr are malicious?

The following npm versions of bubblestr are flagged malicious: 1.1.4. Treat any of these as compromised.

How do I remediate bubblestr if I installed it?

bubblestr 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 bubblestr — how do I know if it already compromised me?

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

Yes — bubblestr is associated with the IN-MAL-2026-006849, GHSA-9p79-38q4-f6wc 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 bubblestr 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 bubblestr (version 1.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bubblestr across your stack and pipelines.

Malicious package

bubblestrnpm

bubblestr is a confirmed malicious npm package (MAL-2026-5930) that steals credentials and exfiltrates sensitive data (malicious version 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bubblestr (npm)

MAL-2026-5930

Immediate action

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

npm uninstall bubblestr

What this malware does

package.json declares "postinstall": "node index.js", and index.js is a heavily obfuscated single-file script (RC4+base64 string-array with rotating shift and two decoder wrappers). After deobfuscation, the postinstall body performs an HTTP GET to a built URL, writes the response body to a file under os.tmpdir() using fs.writeFileSync(..., {flag:'w+'}), and immediately executes the dropped file via child_process.exec(path, {windowsHide:true, cwd: process.cwd()}). This fires automatically on npm install with no user interaction and lands attacker-controlled bytes on the installer's machine. Author and description fields are empty, the obfuscation has no legitimate justification for a 'utility' package, and the README contradicts the published name by instructing users to install/require @array-util/subsearch — a name-confusion lure designed to harvest installs while hiding under a different documented identity. The combination of install-time remote fetch-and-exec, obfuscation intent to evade scanners, and identity mismatch is a textbook supply-chain dropper.

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

1.1.4

Indicators of compromise (SHA-256)

7831cb93037b6f364e2174f6d4fb64b38bac958e54f3653b8a70810681972172

c1c55149f831144e3ea806b4c4a8d9848f9d8ee5d838d4379bb49b3d98915b85

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

Campaign

IN-MAL-2026-006849GHSA-9p79-38q4-f6wc

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bubblestr-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

Explore

All malware advisories How O3 detects malware Vulnerability database