Malicious Code Injection in smart_alpaca-appteadev: A Threat to npm Ecosystem
Summary
MAL-2025-108857: Malicious code in smart_alpaca-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 smart_alpaca-appteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the smart_alpaca-appteadev package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, posing a significant risk to developers and users who rely on the integrity of npm packages. The origin of this issue is traced back to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall smart_alpaca-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 avoid using the smart_alpaca-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The smart_alpaca-appteadev package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant and take immediate action to remove the affected package and monitor their dependencies for vulnerabilities.
See every vulnerability recorded for smart_alpaca-appteadev →
FAQ
The malicious code modifies package metadata and republishes variants to inflate developer reputation scores.
You can use Vulert's playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
You should uninstall the smart_alpaca-appteadev package immediately and monitor for any updates or patches.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json.
Failing to address this vulnerability could lead to compromised application integrity, unauthorized access, and potential exploitation of your software.
