Which versions of nonexistent-package are malicious?

The following npm versions of nonexistent-package are flagged malicious: 99.0.3. Treat any of these as compromised.

How do I remediate nonexistent-package if I installed it?

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

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

Yes — nonexistent-package is associated with the GHSA-wxvr-4mc8-3qvj, IN-MAL-2026-008091 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 nonexistent-package 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 nonexistent-package (version 99.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nonexistent-package across your stack and pipelines.

Malicious package

nonexistent-packagenpm

nonexistent-package is a confirmed malicious npm package (MAL-2026-6936) that steals credentials and exfiltrates sensitive data (malicious version 99.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nonexistent-package (npm)

MAL-2026-6936

Immediate action

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

npm uninstall nonexistent-package

What this malware does

No a static rule matches and no traced behavioral findings were produced for this package version. Nothing in the analyzed artifacts indicates exfiltration, install-time remote code execution, silent-relay, credential distribution, backdoor, or dependency-tree hijack against the installer.

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

99.0.3

Indicators of compromise (SHA-256)

979d3fad162aa5c21126e18c0771d6d9df829c9dfa92d02eb437bd5feb93435a

9393b3fc67ac5c169de7089d2f5100b5cb49af4e2b747b46726660bebc2bf66a

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

Campaign

GHSA-wxvr-4mc8-3qvjIN-MAL-2026-008091

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nonexistent-package-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