Which versions of neural-network-scan are malicious?

The following npm versions of neural-network-scan are flagged malicious: 1.0.1, 1.0.2, 1.0.8, 1.0.9. Treat any of these as compromised.

How do I remediate neural-network-scan if I installed it?

neural-network-scan 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 neural-network-scan — how do I know if it already compromised me?

If neural-network-scan 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 neural-network-scan part of a known attack campaign?

Yes — neural-network-scan is associated with the IN-MAL-2026-006515, IN-MAL-2026-006509, IN-MAL-2026-006511, IN-MAL-2026-006513, IN-MAL-2026-006512, IN-MAL-2026-006514, IN-MAL-2026-006516, IN-MAL-2026-006510 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 neural-network-scan 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 neural-network-scan (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging neural-network-scan across your stack and pipelines.

Malicious package

neural-network-scannpm

neural-network-scan is a confirmed malicious npm package (MAL-2026-5794) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in neural-network-scan (npm)

MAL-2026-5794

Immediate action

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

npm uninstall neural-network-scan

What this malware does

The package ships a collect.js script that imports child_process and performs an HTTP POST carrying host identifiers (hostname referenced multiple times in the same file alongside the POST sink). This pattern — child_process + hostname collection + outbound POST in a non-functional 'scan' utility — matches the host-reconnaissance / data-exfiltration shape used by dependency-confusion and recon-beacon packages. The package name and minimal surface are consistent with a recon lure rather than a useful library. Installing or requiring this package causes installer host data to be sent to an external endpoint.

Malicious versions

4 flagged

1.0.11.0.21.0.81.0.9

Indicators of compromise (SHA-256)

32cd34d7d848f0f64839e9fd009bc22f56f1407049fdfddfb277152fc0dc3e9b

8657017661f8b275b9adef62fddbdc4fce4016c571bd2a1e5dadd9eee9609a53

898c75e5a6ae94d115820736ffd2ca4cb948f72655d5c0175a3432cec835768c

91f7b1fd2b2e20022c3700412be3a333d7fd9a9728f29ba4201bfa7bdf51d68d

a572bf2268bcbcc67e7ef597c16a61ca3aa7a2a87377444ab4e7d48fcea32845

bdcd20372cf130e662ffa5c85d3a9d30d45d71c5c647736c3dfec1d9ee9ca25b

50dd445d8521da8572330c103ed001bdbabc8dca459072073d24f3b50a65602a

51339fa6de09a8ba3910005913acdd754aac96895f7d3f49968e1663bdb95f68

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

Campaign

IN-MAL-2026-006515IN-MAL-2026-006509IN-MAL-2026-006511IN-MAL-2026-006513IN-MAL-2026-006512IN-MAL-2026-006514IN-MAL-2026-006516IN-MAL-2026-006510

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks neural-network-scan-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