Which versions of open-item-validator are malicious?

The following npm versions of open-item-validator are flagged malicious: 1.0.3, 1.0.5. Treat any of these as compromised.

How do I remediate open-item-validator if I installed it?

Remove open-item-validator 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 open-item-validator — how do I know if it already compromised me?

If open-item-validator 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 open-item-validator part of a known attack campaign?

Yes — open-item-validator is associated with the IN-MAL-2026-019720, IN-MAL-2026-019719 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 open-item-validator 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 open-item-validator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging open-item-validator across your stack and pipelines.

Malicious package

open-item-validatornpm

open-item-validator is a confirmed malicious npm package (MAL-2026-16052) that executes malicious code on install (malicious versions 1.0.3, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in open-item-validator (npm)

MAL-2026-16052

Immediate action

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

npm uninstall open-item-validator

What this malware does

On require(), index.js spawns a detached, unref'd background Node process (lib/check-items.js) that repeatedly HTTP-GETs a JSON payload from http://itemx.servegame.com:8888/api/x-realtime and executes the returned JavaScript via new Function('require','module', payload.code)(require, moduleObj). The daemon survives the parent process and re-polls the endpoint on a configured interval, so whoever controls that endpoint runs arbitrary Node code on the installer's host on library load and continuously thereafter. The fetch is over plain HTTP to a No-IP dynamic-DNS host (servegame.com) that does not match the publisher's declared homepage (game.spawnrealm.com); a bundled RSA signature check does not alter that the endpoint operator chooses what code runs. README framing as 'signed game code updates' is inconsistent with the shipped generic fetch-and-exec mechanism and the publisher/destination host mismatch.

Malicious versions

2 flagged

1.0.31.0.5

Indicators of compromise (SHA-256)

7ba5b55d57f4938bf2494d369d14434bb80ba6f6c712c7f8d89ae773c27dc457

ee1ac3d27c505e6a6e95a5544939630fdb29b701cbe41f095d7431cd4a2c83aa

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

Campaign

IN-MAL-2026-019720IN-MAL-2026-019719

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks open-item-validator-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

Explore

All malware advisories How O3 detects malware Vulnerability database