Malicious Code Injection in Changing Whale Requirement Package
Summary
MAL-2025-93504: Malicious code in changing_whale_requirement (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 'changing_whale_requirement' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages with randomized names. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'changing_whale_requirement' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic republishing of these variants. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially affecting other developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_whale_requirementIf 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 remove the 'changing_whale_requirement' package from your project by executing: 'npm uninstall changing_whale_requirement'. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The 'changing_whale_requirement' package has been identified as containing malicious code that compromises the npm registry. It is crucial for developers to update or remove this package to maintain the security and integrity of their applications. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for changing_whale_requirement →
FAQ
The malicious code modifies package.json files, removes private flags, and generates random package names to inflate developer reputation scores.
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.
Using this package can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially introducing security risks to your application.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
If an immediate update is not possible, consider removing the package from your project until a secure version is released.
