Malicious Code Detected in bartok-cli: A Critical npm Vulnerability

bartok-cli Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15484: Malicious code in bartok-cli (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 package bartok-cli is a command-line interface tool designed for various automation tasks within the npm ecosystem. It allows developers to streamline their workflows by providing a set of commands that can be executed in the terminal. However, this package has been found to contain malicious code, posing significant risks to users who rely on it for their development processes.

Vulnerability Detail

The vulnerability in bartok-cli originates from the inclusion of malicious code within the package. This code can potentially compromise user systems, leading to unauthorized access, data breaches, or other harmful activities. The malicious nature of this code makes it imperative for users to take immediate action to protect their systems and data.

How To Fix

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

npm uninstall bartok-cli

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 bartok-cli package from their projects until a secure version is released. This can be done using the command: 'npm uninstall bartok-cli'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the bartok-cli package highlights the importance of vigilance in the open-source ecosystem. Users must take proactive measures to safeguard their systems by updating or removing affected packages. Utilizing tools like Vulert can aid in monitoring vulnerabilities effectively.

See every vulnerability recorded for bartok-cli →

Share this vulnerability

FAQ

bartok-cli is a command-line interface tool for automating tasks in the npm ecosystem.

The specific nature of the malicious code has not been disclosed, but it poses significant risks to user systems.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed bartok-cli, it is recommended to uninstall it immediately and monitor for updates or patches.

Yes, consider exploring other CLI tools that offer similar functionalities without the security risks associated with bartok-cli.

How To Fix

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

npm uninstall bartok-cli

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