Which versions of babel-polyfill-plugin-corejs2 are malicious?

The following npm versions of babel-polyfill-plugin-corejs2 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate babel-polyfill-plugin-corejs2 if I installed it?

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

If babel-polyfill-plugin-corejs2 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 babel-polyfill-plugin-corejs2 part of a known attack campaign?

Yes — babel-polyfill-plugin-corejs2 is associated with the IN-MAL-2026-018647 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 babel-polyfill-plugin-corejs2 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 babel-polyfill-plugin-corejs2 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging babel-polyfill-plugin-corejs2 across your stack and pipelines.

Malicious package

babel-polyfill-plugin-corejs2npm

babel-polyfill-plugin-corejs2 is a confirmed malicious npm package (MAL-2026-14426) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in babel-polyfill-plugin-corejs2 (npm)

MAL-2026-14426

Immediate action

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

npm uninstall babel-polyfill-plugin-corejs2

What this malware does

The package advertises itself as a Babel core-js 2 polyfill plugin, but the shipped lib/index.js contains unrelated web3-core-subscriptions boilerplate followed by a Function() invocation whose body is ~110KB of obfuscated JavaScript (random identifiers, numeric offset arrays, TEA-like mixing routine, unicode-escape string literals). The Function() call executes whenever a consumer require()s the package, running the opaque payload at import time. The declared purpose does not match the shipped code, and the obfuscation is confined to the appended payload rather than being a general minification artifact.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

13878d994b01607c379e26646449b7cca95099f9b2eb5be2e1f8e19aeea32eb3

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

Campaign

IN-MAL-2026-018647

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks babel-polyfill-plugin-corejs2-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