Which versions of json-to-simple-graphql-schema are malicious?

The following npm versions of json-to-simple-graphql-schema are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate json-to-simple-graphql-schema if I installed it?

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

If json-to-simple-graphql-schema 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 json-to-simple-graphql-schema part of a known attack campaign?

Yes — json-to-simple-graphql-schema is associated with the IN-MAL-2026-004779, IN-MAL-2026-004780, GHSA-2qqv-9mw5-52q2 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 json-to-simple-graphql-schema 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 json-to-simple-graphql-schema (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-to-simple-graphql-schema across your stack and pipelines.

Malicious package

json-to-simple-graphql-schemanpm

Malicious code in json-to-simple-graphql-schema (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4590

Immediate action

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

npm uninstall json-to-simple-graphql-schema

What this malware does

The package contains a poc.js script that collects host reconnaissance data (os.hostname(), os.platform(), output of whoami via child_process) and POSTs it to a remote endpoint over https.request. The combination of os/system enumeration, child_process command execution (e.g. whoami), and an outbound HTTPS POST in the same file is the canonical host-reconnaissance and exfiltration shape. The package name suggests a JSON-to-GraphQL schema converter, and there is no legitimate reason for such a converter to ship a script that runs whoami, reads host identity, and ships the results off-host. Installing or executing this package gives the publisher tangible host reconnaissance data from the installer's machine.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b9998f4fd6abaaefcf6bd610ce0b558f0e1eb22c9d4dae07a111c27cc7f7322c

cb3cc7123da62361aded02aa515ca0d6ff88f032bd247329a1acf079bfa888b0

aac4fc25ca9c9d5b64e66c565f14cd4f07873a2e716834ba633239df20a99bab

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

Campaign

IN-MAL-2026-004779IN-MAL-2026-004780GHSA-2qqv-9mw5-52q2

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks json-to-simple-graphql-schema-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