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

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

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

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

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

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

Malicious package

transform-es2015-sticky-regexnpm

Malicious code in transform-es2015-sticky-regex (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10136

Immediate action

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

npm uninstall transform-es2015-sticky-regex

What this malware does

package.json declares both a dependency and a devDependency on 'transform-es2015-sticky-regex' pointing at http://pack.nppacks.com/npm/transform-es2015-sticky-regex. On npm install, npm fetches whatever tarball that plain-HTTP, non-registry host currently serves and installs it into node_modules with no version pin and no integrity hash — the maintainer of pack.nppacks.com can substitute arbitrary code at any time and it will land in the installer's dependency tree on the next install. The package name is also a namespace-confusion of the well-known 'babel-plugin-transform-es2015-sticky-regex' (Babel plugin naming convention prefixes 'babel-plugin-'); the shipped index.js does not implement the sticky-regex transform but a DefinePlugin-style identifier replacer, and a source comment states the package is 'for Security Research Testing Purpose'. Additional network-capable dependencies (axios, node-fetch, ws) are declared but unused by the shipped code, pre-staging network primitives for whatever the swapped tarball chooses to import.

Malicious versions

1 flagged

6.24.3

Indicators of compromise (SHA-256)

eadf76ef8e123f9ce50c2910c71912996a3d079a91076ffed8d29830a1687ae1

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

Campaign

IN-MAL-2026-009622

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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