Critical Malware Alert: pino-sdk-v2 Package Exfiltrates Sensitive Data

pino-sdk-v2 Updated 06 Mar 2026

Summary

06/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1259: Malicious code in pino-sdk-v2 (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 Penetration testing for web, API and mobile 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-v2 package is a Node.js library designed for logging purposes, providing a fast and efficient way to handle log data. However, this package has been compromised, leading to significant security concerns. The malicious version of pino-sdk-v2 impersonates the legitimate pino package but includes harmful code that can exfiltrate sensitive information from users' environments.

Vulnerability Detail

The vulnerability in the pino-sdk-v2 package arises from malicious code embedded in the modified 'package/lib/tools.js' file. This code is designed to exfiltrate keys from the .env file to a Discord webhook, potentially exposing sensitive credentials and configuration data. The implications of this vulnerability are severe, as it can lead to unauthorized access to systems and data breaches.

How To Fix

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

npm uninstall pino-sdk-v2

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 workaround, users can remove the pino-sdk-v2 package from their project until a secure version is released. This can be done by running the command: 'npm uninstall pino-sdk-v2'. Additionally, consider using alternative logging libraries that do not have known vulnerabilities.

Conclusion

The pino-sdk-v2 package has been compromised, leading to a critical vulnerability that can expose sensitive information. Users are urged to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for pino-sdk-v2 →

Share this vulnerability

FAQ

pino-sdk-v2 is a Node.js logging library that provides efficient logging capabilities for applications.

The malware exfiltrates sensitive keys from the .env file and sends them to a Discord webhook, compromising user security.

The risks include unauthorized access to sensitive information, potential data breaches, and compromised application security.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not possible, consider removing the package and using alternative logging solutions until a secure version is available.

How To Fix

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

npm uninstall pino-sdk-v2

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