Malicious Code Injection in selective_alpaca_violet-53: npm Package Vulnerability
Summary
MAL-2025-108509: Malicious code in selective_alpaca_violet-53 (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 'selective_alpaca_violet-53' 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 its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'selective_alpaca_violet-53' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers using this package, as it can lead to unauthorized access and manipulation of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall selective_alpaca_violet-53If 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 remove the 'selective_alpaca_violet-53' package from your project by executing 'npm uninstall selective_alpaca_violet-53'. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The 'selective_alpaca_violet-53' package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for selective_alpaca_violet-53 →
FAQ
The vulnerability involves malicious code that alters package metadata and republish behavior, compromising the integrity of the npm registry.
You can use Vulert to monitor your application for vulnerabilities by analyzing your package-lock.json file. Visit Vulert Scanner to check without any signup.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the nature of the malicious code suggests potential for unauthorized access and manipulation.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
