Critical Malicious Code Vulnerability in pino-sdk Package

pino-sdk Updated 13 Mar 2026

Summary

13/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1399: Malicious code in pino-sdk (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The pino-sdk package is a popular logging library for Node.js applications, designed to provide high-performance logging capabilities. It is widely used in various applications for its efficiency and ease of integration. However, recent findings have revealed that this package has been compromised, leading to significant security concerns for users who have it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the pino-sdk package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information, including secrets and keys. The origin of this vulnerability is linked to a malicious actor who embedded harmful code in the package, which can lead to severe ramifications for affected users, including data breaches and loss of control over their systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pino-sdk

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users should ensure that the pino-sdk package is not running in their applications. Additionally, consider using alternative logging libraries until the issue is resolved.

Conclusion

The pino-sdk package has been identified as containing malicious code that poses a significant risk to users. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor for updates and consider alternative logging solutions until the issue is resolved.

See every vulnerability recorded for pino-sdk →

Share this vulnerability

FAQ

Immediately remove the pino-sdk package and rotate any sensitive information stored on the affected machine.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Currently, there is no patch available. It is recommended to remove the package until a secure version is released.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.

It is highly discouraged to continue using pino-sdk due to the embedded malicious code. It is best to remove it and look for alternatives.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pino-sdk

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback