Which versions of nitro-graphql are malicious?

The following npm versions of nitro-graphql are flagged malicious: 1.5.12. Treat any of these as compromised.

How do I remediate nitro-graphql if I installed it?

nitro-graphql 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 nitro-graphql — how do I know if it already compromised me?

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

Yes — nitro-graphql is associated with the GHSA-8q6q-44gw-jhxc 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 nitro-graphql 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 nitro-graphql (version 1.5.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nitro-graphql across your stack and pipelines.

Malicious package

nitro-graphqlnpm

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

MAL-2025-191131

Immediate action

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

npm uninstall nitro-graphql

What this malware does

The package nitro-graphql 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

1.5.12

Indicators of compromise (SHA-256)

a77bf7f130d454574e5e838c6ce7922e015408f32542a4b15e77d26698129fe3

9d9128d286b987c395f12fe075844ca1d636ead245a3f0ef578b62255768a8be

36ef7661deeec20f2ea8ef1c642811be2a627ee5e8b6a3f51cd61de1e421547b

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

Campaign

GHSA-8q6q-44gw-jhxc

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nitro-graphql-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