Which versions of syntax-async-functions are malicious?

Every published version of syntax-async-functions on npm is considered malicious. Remove the package entirely.

How do I remediate syntax-async-functions if I installed it?

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

If syntax-async-functions 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 syntax-async-functions part of a known attack campaign?

Yes — syntax-async-functions is associated with the GHSA-vw4x-22x4-cvmw 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 syntax-async-functions 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 syntax-async-functions (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging syntax-async-functions across your stack and pipelines.

Malicious package

syntax-async-functionsnpm

Malicious code in syntax-async-functions (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-559

Immediate action

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

npm uninstall syntax-async-functions

What this malware does

The package syntax-async-functions 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)

825f3136b24c0d7a3f9a0fbf93844f4b33182c384bf5146da86fed7d04160b7a

a0d14dae07d53bcd3b3da9693bf5facb7518fafafe8cc2c54d93cd59ec7a28f1

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 syntax-async-functions (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging syntax-async-functions across your stack and pipelines.
If you installed it — respond
Remove syntax-async-functions 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 syntax-async-functions 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 syntax-async-functions 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. syntax-async-functions 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-vw4x-22x4-cvmw

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks syntax-async-functions-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