Malicious Code Detected in bashlog Package - Security Alert

bashlog Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15504: Malicious code in bashlog (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 bashlog package is an npm library designed for logging bash commands and outputs. It is commonly used in applications that require command-line interaction and logging capabilities. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the bashlog package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall bashlog

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 bashlog package from their project until a secure version is released. This can be done using the command: npm uninstall bashlog. Consider using alternative logging libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the bashlog package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications.

See every vulnerability recorded for bashlog →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive information and execute harmful commands within the user's environment.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you determine if your application is affected.

Yes, Vulert allows you to check for vulnerabilities using just your package-lock.json file, without requiring any installations or code access.

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

Detailed information about the bashlog vulnerability can be found on the GitHub repository and various security advisory platforms.

How To Fix

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

npm uninstall bashlog

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