Malicious Code Injection in musik-ddai-bot: A Threat to npm Users

musik-ddai-bot Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161039: Malicious code in musik-ddai-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 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 musik-ddai-bot package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is intended to facilitate specific functionalities within applications but has been compromised. The vulnerability stems from its association with a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names.

Vulnerability Detail

The vulnerability in musik-ddai-bot originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to users who may unknowingly install these compromised packages, leading to potential security breaches and loss of data integrity.

How To Fix

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

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

Conclusion

The musik-ddai-bot package has been compromised, posing significant risks to users within the npm ecosystem. It is crucial to remain vigilant, update packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, users can safeguard their applications against potential threats.

See every vulnerability recorded for musik-ddai-bot →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and floods the npm registry with compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If you have installed musik-ddai-bot, it is recommended to uninstall the package and check for any updates or patches before reinstalling.

While specific exploits have not been detailed, the nature of the vulnerability suggests that it could lead to unauthorized access or data manipulation.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall musik-ddai-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