Which versions of transform-async-to-generator are malicious?

Every published version of transform-async-to-generator on npm is considered malicious. Remove the package entirely.

How do I remediate transform-async-to-generator if I installed it?

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

If transform-async-to-generator 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 transform-async-to-generator part of a known attack campaign?

Yes — transform-async-to-generator is associated with the GHSA-cxhp-v2gh-3v7f 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-async-to-generator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for transform-async-to-generator (all published versions).

Malicious package

transform-async-to-generatornpm

Advisory published Jan 28, 2026Updated Feb 2, 2026

transform-async-to-generator is a confirmed malicious npm package (MAL-2026-560) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in transform-async-to-generator (npm)

MAL-2026-560

Immediate action

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

npm uninstall transform-async-to-generator

What this malware does

The package transform-async-to-generator was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

7b8bbde410fd2a91ea87426009ce9bffcbcf7c68b03729d43441fb60ac36d51e

3375385fb6c066445341256f9ce616582a713468ea0649853056c24b4aaf1776

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for transform-async-to-generator (all published versions).
If you installed it — respond
Remove transform-async-to-generator 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-async-to-generator 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. transform-async-to-generator on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cxhp-v2gh-3v7f

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks transform-async-to-generator-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