Which versions of transform-es2015-unicode-regex are malicious?

The following npm versions of transform-es2015-unicode-regex are flagged malicious: 6.24.1. Treat any of these as compromised.

How do I remediate transform-es2015-unicode-regex if I installed it?

transform-es2015-unicode-regex is a typosquat — you almost certainly intended a legitimately-named package. Remove transform-es2015-unicode-regex, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed transform-es2015-unicode-regex — how do I know if it already compromised me?

If transform-es2015-unicode-regex 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 transform-es2015-unicode-regex part of a known attack campaign?

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

Malicious package

transform-es2015-unicode-regexnpm

transform-es2015-unicode-regex is a confirmed malicious npm package (MAL-2026-13612) that typosquats a legitimate package to trick installs (malicious version 6.24.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in transform-es2015-unicode-regex (npm)

MAL-2026-13612

Immediate action

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

npm uninstall transform-es2015-unicode-regex

What this malware does

package.json declares the package's own name as a dependency (and devDependency) with the specifier http://pack.nppacks.com/npm/transform-es2015-unicode-regex, a plain-HTTP, non-registry, third-party host unrelated to the legitimate babel-plugin-transform-es2015-unicode-regex it name-resembles. When a consumer runs npm install, npm fetches whatever tarball that URL currently returns and installs it, running any lifecycle scripts and making the fetched code require-able — arbitrary install-time code execution controlled by the operator of pack.nppacks.com, over an unauthenticated cleartext channel that is also trivially MITM-able. The package's index.js is not the referenced Babel plugin's code and carries a self-labeled 'Security Research Testing Purpose' comment; the name mimics babel-plugin-transform-es2015-unicode-regex, increasing the chance of accidental installation.

Malicious versions

1 flagged

6.24.1

Indicators of compromise (SHA-256)

e85a13111400ea4b22bb2ae0d51ad784a89bc548d56b496a855bf7e6d6595804

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for transform-es2015-unicode-regex (version 6.24.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging transform-es2015-unicode-regex across your stack and pipelines.
If you installed it — respond
transform-es2015-unicode-regex is a typosquat — you almost certainly intended a legitimately-named package. Remove transform-es2015-unicode-regex, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If transform-es2015-unicode-regex 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 transform-es2015-unicode-regex 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. transform-es2015-unicode-regex on npm has been identified as a malicious package (version 6.24.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017082

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks transform-es2015-unicode-regex-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