Malicious Code Injection in melted_whale-appteadev: A Threat to npm Ecosystem
Summary
MAL-2025-105791: Malicious code in melted_whale-appteadev (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'melted_whale-appteadev' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'melted_whale-appteadev' originates from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and users relying on legitimate packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult to trace and mitigate the impact.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall melted_whale-appteadevIf 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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies to known safe versions. You can also utilize tools like Vulert to monitor your project for vulnerabilities. For instance, you can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'melted_whale-appteadev' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to maintain the security of their applications.
See every vulnerability recorded for melted_whale-appteadev →
FAQ
The vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising user applications.
You can check your package.json and package-lock.json files for any references to melted_whale-appteadev or use npm audit to identify vulnerabilities in your dependencies.
No, the best course of action is to uninstall the package as it is inherently malicious and does not have a secure version.
You should immediately uninstall the package using 'npm uninstall melted_whale-appteadev' and review your project for any other potentially compromised packages.
Vulert monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access or installation.
