Which versions of nonenull1 are malicious?

The following npm versions of nonenull1 are flagged malicious: 1.0.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.5.2. Treat any of these as compromised.

How do I remediate nonenull1 if I installed it?

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

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

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

Malicious package

nonenull1npm

Malicious code in nonenull1 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10090

Immediate action

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

npm uninstall nonenull1

What this malware does

On npm install, [email protected] auto-executes a credential stealer via node-gyp. package.json sets gypfile: true, and the shipped binding.gyp declares no native sources but places a GYP command-expansion <!(node index.js...) in the sources array, so node-gyp rebuild runs index.js during the configure step (an implicit install hook that is not declared as scripts.postinstall). index.js then: (1) collects host fingerprint (os.hostname, os.userInfo, process.platform, cwd, node version, git user.email) and POSTs it to https://crabbing-thong-overhung.ngrok-free.dev/ping; (2) reads every file in ~/.ssh, ~/.aws, ~/.config, ~/.kube, ~/.docker, and ~/.gnupg, plus every.env* file discovered walking 8 directory levels up from cwd, and POSTs the contents to /exfil at the same host; (3) filters process.env for keys matching token|secret|key|pass|pwd|auth|api|cred|jwt|cookie and exfiltrates those values. The destination is a hardcoded ngrok tunnel controlled by the publisher. This is a textbook installer-side credential stealer with an implicit install hook designed to evade manifest-only scanners.

The OpenSSF Package Analysis project identified 'nonenull1' @ 1.5.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

6 flagged

1.0.01.2.01.3.01.4.01.5.01.5.2

Indicators of compromise (SHA-256)

1c4b3bf7033e97a761dda8961152a0325d3eb9e89b6cddc4b838176ae13e0568

925481cdd4c7bb74f55623377798b53978d16a19b67d4c9e869c042b716b59cb

aa83c8718f9869244a68bd577a3e013e16428235357ae774ad8968c101cede32

b7b1ed48fcae410e28bdade3bf5a715b8c4b1390e43591f8263964d8ee302b43

5f02ee2873da4d092fe8c8cc7418db3d2c661a64e5015eb0505fe26e5979da80

73d50f95c05f103c28463abdeff6ebf402d5a23abdc0ef3429d20a105237c966

bf2530ede2ed0c04e03f8810e9ca789a38102fdf0cdeb61dd629cb1b522accd0

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

Campaign

IN-MAL-2026-009320IN-MAL-2026-009319IN-MAL-2026-009321IN-MAL-2026-009303

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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