Which versions of items-validator are malicious?

The following npm versions of items-validator are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate items-validator if I installed it?

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

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

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

Malicious package

items-validatornpm

items-validator is a confirmed malicious npm package (MAL-2026-17235) that executes malicious code on install (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in items-validator (npm)

MAL-2026-17235

Immediate action

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

npm uninstall items-validator

What this malware does

On require, index.js invokes initializeDaemon() at top level, which uses spawn('node', [lib/check-items.js], { detached: true, stdio: 'ignore' }) followed by child.unref() to launch a persistent background process independent of the parent. The daemon HTTP-GETs a JSON payload from the hardcoded endpoint https://game.spawnrealm.com/api/item-realtime?key=abcdef123456 and passes payload.code to new Function('require', 'module', payload.code), executing server-supplied JavaScript inside the installer's Node process with full require access. An RSA signature check is performed against a public key bundled in the package (crypto-config.js), so the author controls both the signing key and the verifier and the check provides no independent integrity guarantee. Anyone controlling game.spawnrealm.com — including via DNS or TLS — can run arbitrary code as the installing user for the lifetime of the host process. The package is advertised as a validator library, and this remote-code-loader behavior is undisclosed and unrelated to the stated purpose.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

a8e49b1abd7c566b17104c5a2823251df2ca253a0fa509d7c19db1c1942ad13d

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

Campaign

IN-MAL-2026-020612

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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