Malicious Code Injection in musik-dai-normal Package

musik-dai-normal Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161033: Malicious code in musik-dai-normal (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 musik-dai-normal package is part of the npm ecosystem and is typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. The package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in the musik-dai-normal package stems from its association with the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of dependent applications. This can lead to unauthorized access, data breaches, and a loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall musik-dai-normal

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 prevent the installation of the malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your package-lock.json file does not include musik-dai-normal. You can also use the following command to audit your project for vulnerabilities: npm audit.

Conclusion

The musik-dai-normal package poses a significant security risk due to its malicious code designed to manipulate npm's package management system. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for musik-dai-normal →

Share this vulnerability

FAQ

The musik-dai-normal package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.

If you have installed the musik-dai-normal package, you should uninstall it immediately using the command: npm uninstall musik-dai-normal.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Currently, there are no patches available for the musik-dai-normal package. The best course of action is to remove the package and monitor your dependencies for updates.

How To Fix

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

npm uninstall musik-dai-normal

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