Critical Malicious Code Vulnerability in bartok-script-sdk Package

bartok-script-sdk Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15489: Malicious code in bartok-script-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 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 bartok-script-sdk is an npm package designed to facilitate script execution and automation within the Bartok framework. It provides developers with tools to streamline their workflow and enhance productivity. However, this package has been identified as containing malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the bartok-script-sdk package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall bartok-script-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 workaround, users can avoid using the bartok-script-sdk package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing security measures such as code reviews and dependency scanning to identify and mitigate vulnerabilities.

Conclusion

The discovery of malicious code in the bartok-script-sdk package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to remove the affected package and seek alternatives to safeguard their applications.

See every vulnerability recorded for bartok-script-sdk →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and may lead to exploitation of the affected application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check your application without any signup.

If no alternatives are available, consider reaching out to the community for recommendations or explore modifying your application's architecture to eliminate reliance on this package.

Implementing regular dependency audits, using tools like Vulert, and keeping your packages updated can help prevent similar vulnerabilities.

Failure to address this vulnerability could lead to severe security breaches, data loss, and damage to your application's reputation.

How To Fix

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

npm uninstall bartok-script-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