pino-std
Affected
- Versions:
7.2.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in pino-std (npm)
pino-std ships lib/contract.js, byte-identical to the pino-testkit payload: a copy of the pino logger with an extra obfuscated module that decodes and evaluates code at load. It is a new name for the pino-testkit (MAL-2026-16484) campaign; the file hashes below match that record's evidence. The package presents itself as an ordinary utility, so the code runs on import or install without the user knowing.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (252ced7b2337bba36d5947f3d974c51d118a54661c1b59ef0dbc706cb3d44fc0)
The package name resembles the legitimate pino-std-serializers and the tarball reproduces that project's source files, README, and author metadata nearly verbatim. In addition, it ships an undocumented file lib/contract.js that is not referenced from index.js, the README, or any lifecycle script. contract.js reconstructs a function body from a character-shuffled/char-code-substituted string and executes it via the Function constructor reached indirectly through a prototype's constructor property (ype.constructor). The same file stashes the Node require function into a global variable before invoking the reconstructed code, which lets the hidden payload load arbitrary built-in and installed modules once reached. The combination of a lookalike package name, verbatim copying of an upstream project to serve as cover, an added undocumented file that runtime-assembles and executes opaque code, and a global-require stash is the shape of a dormant/second-stage loader rather than legitimate functionality. The payload is not invoked from the package's main entry or from a lifecycle hook, so installing or requiring pino-std does not auto-detonate it in a default npm install; execution requires the file to be reached by a consumer or a later-added import.
Not rated by the source.
7.2.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0