Critical Malicious Code Vulnerability in logbin-nodejs Package

logbin-nodejs Updated 02 Oct 2025

Summary

27/05/2025
CRITICAL
No i
Critical
Not published

MAL-2025-4487: Malicious code in logbin-nodejs (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

logbin-nodejs is an npm package designed for logging and data management in Node.js applications. It is widely used for its simplicity and efficiency in handling logs. However, the package has been compromised, leading to severe security risks for any system utilizing it. The malicious code embedded within this package can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from a malicious code injection in the logbin-nodejs package, identified by the ID MAL-2025-4487. This code can fully compromise any computer that has the package installed or running, allowing attackers to access sensitive information such as secrets and keys. The ramifications include potential data breaches and complete system takeover, making it imperative for users to act swiftly.

How To Fix

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

npm uninstall logbin-nodejs

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, you can isolate the affected system from the network to prevent further unauthorized access. However, this does not eliminate the malicious code and should not be considered a permanent solution.

Conclusion

The logbin-nodejs package has been compromised with malicious code, posing significant risks to any system using it. Immediate action is required to remove the package and secure sensitive data. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for logbin-nodejs →

Share this vulnerability

FAQ

logbin-nodejs is an npm package used for logging and managing data in Node.js applications.

If you have the logbin-nodejs package installed, your system is potentially compromised. You can use Vulert to check for vulnerabilities in your application.

Immediately rotate all secrets and keys stored on the compromised system from a secure computer.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time.

It is recommended to find an alternative package or wait for a secure version before considering its use again.

How To Fix

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

npm uninstall logbin-nodejs

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