Malicious Code Injection in musik-dait-bot Package

musik-dait-bot Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161035: Malicious code in musik-dait-bot (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The musik-dait-bot package is part of the npm ecosystem, designed for music-related functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is engineered to manipulate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the musik-dait-bot package stems from its involvement in a token reward campaign that utilizes malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently expose their applications to malicious code.

How To Fix

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

npm uninstall musik-dait-bot

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 avoid using the musik-dait-bot package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The musik-dait-bot package is compromised by malicious code that can lead to significant security risks. It is crucial to update to a patched version or remove the package entirely. Utilizing tools like Vulert can help in monitoring and preventing such vulnerabilities in the future.

See every vulnerability recorded for musik-dait-bot →

Share this vulnerability

FAQ

The musik-dait-bot package is an npm package designed for music-related functionalities but has been compromised by malicious code.

The malicious code can modify your package.json file, leading to potential security vulnerabilities and the pollution of the npm registry.

If you have installed the musik-dait-bot package, you should remove it and update to a secure version or use an alternative package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

Regularly update your packages, use trusted sources, and employ tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall musik-dait-bot

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