Which versions of nat-ulid are malicious?

The following npm versions of nat-ulid are flagged malicious: 3.0.2. Treat any of these as compromised.

How do I remediate nat-ulid if I installed it?

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

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

Yes — nat-ulid is associated with the GHSA-wgqj-fphq-9x3q, IN-MAL-2026-009525 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 nat-ulid 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 nat-ulid (version 3.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nat-ulid across your stack and pipelines.

Malicious package

nat-ulidnpm

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

Malicious code in nat-ulid (npm)

MAL-2026-5880

Immediate action

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

npm uninstall nat-ulid

What this malware does

The package ships a bundled file at dist/node/payload.js containing several POST call sites (around lines 14592, 14621, 14805, 14923, 15805). Pattern matches alone cannot distinguish a legitimate HTTP client library from an exfiltration channel: the destinations may be configurable parameters of an exposed API, documented vendor endpoints, or attacker-controlled hosts. No corroborating behavior such as credential reads, environment scraping, install-time lifecycle execution, or known-bad infrastructure was identified in the available evidence. Routing to human review for semantic verification of the bundle's POST destinations and reachability.

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

3.0.2

Indicators of compromise (SHA-256)

86093a5f138b04098b5998320eba1e20458181cbc3b0d71e27cb3aa234245396

ab95c3f95c377215b7cbd4be6d2cdcc79304910b03a2dcdf08f65da6f1c05f4c

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

Campaign

GHSA-wgqj-fphq-9x3qIN-MAL-2026-009525

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nat-ulid-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