Which versions of os-ulid-void are malicious?

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

How do I remediate os-ulid-void if I installed it?

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

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

Yes — os-ulid-void is associated with the GHSA-7fhf-p3wv-2xrc, IN-MAL-2026-009477 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 os-ulid-void 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 os-ulid-void (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 os-ulid-void across your stack and pipelines.

Malicious package

os-ulid-voidnpm

Malicious code in os-ulid-void (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5348

Immediate action

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

npm uninstall os-ulid-void

What this malware does

The package ships a minified file at dist/payload.js where multiple HTTP POST call sites appear (lines 14503, 14532, 14716, 14834, 15716). The literal evidence captured is only the keyword 'POST' without surrounding context, so the destinations, request bodies, and reachability (install-time vs import-time vs explicit user-call) cannot be determined from the available signals. The package name resembles common ULID utility naming and may be a confusion candidate, but no concrete installer-harm code path (env-var scrape, credential read, hardcoded attacker endpoint, dropper, lifecycle hook tied to an exfil call) has been verified. Manual review of dist/payload.js is recommended to confirm whether the POST sites target attacker-controlled destinations or are part of legitimate API surface.

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)

531ba01f5b5d2442cc8070ae6feec31976f9b67957fa3b0936c2cea7b6034b81

ae1f330082068d43b4ef645b06ce190fb0354367ab0d98edadd3f15c6c99dea1

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 os-ulid-void (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 os-ulid-void across your stack and pipelines.
If you installed it — respond
os-ulid-void 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 os-ulid-void 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 os-ulid-void 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. os-ulid-void 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-7fhf-p3wv-2xrcIN-MAL-2026-009477

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks os-ulid-void-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