Which versions of babelcode_js are malicious?

The following npm versions of babelcode_js are flagged malicious: 99.12.9. Treat any of these as compromised.

How do I remediate babelcode_js if I installed it?

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

If babelcode_js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is babelcode_js part of a known attack campaign?

Yes — babelcode_js is associated with the RLMA-2026-04954, RLUA-2026-06079 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 babelcode_js across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for babelcode_js (version 99.12.9).

Malicious package

babelcode_jsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

babelcode_js is a confirmed malicious npm package (MAL-2026-7216) that executes malicious code on install (malicious version 99.12.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in babelcode_js (npm)

MAL-2026-7216

Immediate action

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

npm uninstall babelcode_js

Malicious versions

1 flagged

99.12.9

Indicators of compromise (SHA-256)

bb3e9088c2b1305f2dc4a238cc94c91fc389b1cf0961f2b3562120588308ff3a

abd617ce623cb9a211dc7f6ac6f1ff40f969b01c333808e0e747057ed05982e2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for babelcode_js (version 99.12.9).
If you installed it — respond
Remove babelcode_js 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 babelcode_js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. babelcode_js on npm has been identified as a malicious package (version 99.12.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04954RLUA-2026-06079

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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