OpenSSF/OSV advisory MAL-2026-4600 confirms this npm version as malicious. Package advertises itself via a verbatim copy of pino's README, docs/, and index.d.ts (TypeScript types and documentation are pino's), but index.js does not implement a logger. The exported middleware unconditionally calls a helper that spawns `node./lib/caller.js` with `detached: true`, `stdio: 'ignore'`, and `child.unref()` on every invocation (index.js lines 31-37), disconnecting the child from the parent's...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in loading-session (npm)
Details
Package advertises itself via a verbatim copy of pino's README, docs/, and index.d.ts (TypeScript types and documentation are pino's), but index.js does not implement a logger. The exported middleware unconditionally calls a helper that spawns `node./lib/caller.js` with `detached: true`, `stdio: 'ignore'`, and `child.unref()` on every invocation (index.js lines 31-37), disconnecting the child from the parent's stdout/stderr. The referenced `lib/caller.js` is absent from this version's tarball, so the spawn fails at runtime today, but the launcher shape is structurally a dropper. Shipped alongside is `lib/const.js`, which stores base64-wrapped fields under credential-shaped names (`DEV_API_KEY`, `DEV_SECRET_KEY`, `DEV_SECRET_VALUE`); the `DEV_API_KEY` value decodes to an anonymous JSON-storage URL on api.jsonstorage.net, a host commonly abused for mutable second-stage payload delivery and exfiltration. The combination — pino documentation deception used as cover, covert detached child-process launcher in the only exported function, and a base64-obfuscated anonymous-storage endpoint with credential-shaped siblings — is the staging shape of a dropper/C2 client, not a logger.
## Source: ghsa-malware (21c816f86c4c9a13a7e36fb8b577c766cc64f25ab53466d6f12feeb91e0c4524) 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.
Decision reason
OpenSSF Malicious Packages via OSV confirms loading-session@4.2.1 as malicious (MAL-2026-4600): Malicious code in loading-session (npm)