Which versions of ngx-wooapi are malicious?

The following npm versions of ngx-wooapi are flagged malicious: 12.0.1. Treat any of these as compromised.

How do I remediate ngx-wooapi if I installed it?

ngx-wooapi is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ngx-wooapi — how do I know if it already compromised me?

If ngx-wooapi 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 ngx-wooapi part of a known attack campaign?

Yes — ngx-wooapi is associated with the GHSA-c933-f7h3-47xj 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 ngx-wooapi 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 ngx-wooapi (version 12.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ngx-wooapi across your stack and pipelines.

Malicious package

ngx-wooapinpm

Malicious code in ngx-wooapi (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191130

Immediate action

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

npm uninstall ngx-wooapi

What this malware does

The package ngx-wooapi 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

12.0.1

Indicators of compromise (SHA-256)

6bafe828b44a7293999ec4bd01079f40fff2fe77bb43d6990dc20bcbc6b83162

f966968679e589608ab4bebea12709f14f0e34f77f5ee39e330a7ac84dee9ac4

64a7e8ff946dd01747d5da4806be36032cebaf9ed78da76e88680ece90c066be

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ngx-wooapi (version 12.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ngx-wooapi across your stack and pipelines.
If you installed it — respond
ngx-wooapi is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ngx-wooapi 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 ngx-wooapi 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. ngx-wooapi on npm has been identified as a malicious package (version 12.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c933-f7h3-47xj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ngx-wooapi-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring