Which versions of alloy-graphql are malicious?

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

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

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

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

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

Malicious package

alloy-graphqlnpm

alloy-graphql is a confirmed malicious npm package (MAL-2026-16063) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in alloy-graphql (npm)

MAL-2026-16063

Immediate action

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

npm uninstall alloy-graphql

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. The script collects hostname, username, home directory, DNS servers, current working directory, and package.json contents, and reads /etc/passwd and /etc/hosts from the installer's host. The collected data is HTTPS-POSTed to a hardcoded Burp Collaborator subdomain at ipbtwv9063nc5hvhodh0s4u9x03rrhf6.oastify.com. The package has no advertised functionality beyond this exfiltration payload.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

80ee3815d12ec95aedb4bbe0d3de5c516e99163ca1eba52c2a3de7038b9a2ac0

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

Campaign

IN-MAL-2026-019744

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks alloy-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

Explore

All malware advisories How O3 detects malware Vulnerability database