pino-std@7.2.0
OpenSSF/OSV Malicious Advisory
imported 3h ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18692 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The obfuscated dynamic-code loader is a real, separately callable payload carrier, but source inspection did not establish what its payload does or that the package's main entrypoint reaches it. This supports a warning for unresolved risk, not a confirmed attack.
Independent scan evidence
public snapshot- lib/contract.js contains an obfuscated string reconstruction path that creates generated code.
- Calling the generated function is reachable inside the separately exported contract() function.
- The loader's payload behavior is not resolved by static inspection.
- package.json declares index.js as the main entrypoint and lists no install lifecycle script.
- index.js exports serializers and wrappers without importing lib/contract.js.
Source & flagged code
6 flaggedSource contains an obfuscated payload loader that reconstructs and executes hidden code.
lib/contract.jsView on unpkg · L2lib/contract.js contains an obfuscated string reconstruction path that creates generated code.
lib/contract.jsView on unpkg · L4Calling the generated function is reachable inside the separately exported contract() function.
lib/contract.jsFindings
Affected versions and remediation
This report applies to pino-std@7.2.0.
See all versions of pino-std for other recorded verdicts.
- Avoid installing pino-std@7.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.