Which versions of pino-ulid are malicious?

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

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

pino-ulid is a typosquat — you almost certainly intended a legitimately-named package. Remove pino-ulid, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed pino-ulid — how do I know if it already compromised me?

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

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

Malicious package

pino-ulidnpm

pino-ulid is a confirmed malicious npm package (MAL-2026-16154) that typosquats a legitimate package to trick installs (malicious version 2.12.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pino-ulid (npm)

MAL-2026-16154

Immediate action

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

npm uninstall pino-ulid

What this malware does

pino-ulid impersonates the popular pino and ulid packages (homepage points at github.com/ulid/javascript) and ships a genuine ULID code path as cover. The package.json postinstall hook runs node dist/node/utils.js, which spawns dist/node/payload.js detached with stdio ignored and unref'd, gated by a minimum CPU-count check (sandbox evasion) and a prior-install check against schtasks / HKCU Run / launchd / systemd / autostart. The bundled 466 KB dist/node/payload.js self-labels as Package-bin Agent - Bundled payload, includes the ws client, decodes a hardcoded configuration via Buffer.from(enc, 'base64'), derives a per-host id via getSystemMachineId/defaultAgentId, and opens a WebSocket control channel. Its ws.on('message',...) handler reaches execSync/spawnSync sinks and writes attacker-supplied task.contentBase64 bytes to disk via writeFile, providing remote shell execution and arbitrary file drop on the installer's host. The agent installs cross-platform boot persistence: a systemd user unit at ~/.config/systemd/user/pkg-agent.service and/or ~/.config/autostart/pkg-agent.desktop on Linux, ~/Library/LaunchAgents/com.launchkeeper.pkg-agent.plist on macOS, and a Task Scheduler entry plus HKCU\Software\Microsoft\Windows\CurrentVersion\Run value pkg-agent on Windows. Running npm install pino-ulid installs a persistent remotely-controlled agent unrelated to the advertised ULID functionality.

Malicious versions

1 flagged

2.12.3

Indicators of compromise (SHA-256)

ade54621ac8726adc77fa29c4176808cdf82d0d1f8e45c2e051a17b1fd515779

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pino-ulid (version 2.12.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-ulid across your stack and pipelines.
If you installed it — respond
pino-ulid is a typosquat — you almost certainly intended a legitimately-named package. Remove pino-ulid, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If pino-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 pino-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. pino-ulid on npm has been identified as a malicious package (version 2.12.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020043

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pino-ulid-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database