Malicious Code Injection in colonial_canidae-appteadev: A Threat to npm Users
Summary
MAL-2025-100665: Malicious code in colonial_canidae-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 colonial_canidae-appteadev is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through the automatic generation and publication of derivative packages. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the colonial_canidae-appteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, posing significant risks to developers by inflating reputation scores fraudulently and potentially leading to the distribution of compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall colonial_canidae-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 remove the colonial_canidae-appteadev package from your project by executing: npm uninstall colonial_canidae-appteadev. This will prevent any malicious scripts from executing until a secure version is available.
Conclusion
The colonial_canidae-appteadev package poses a significant risk due to embedded malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for colonial_canidae-appteadev →
FAQ
The main risk is the potential for malicious code to alter your project's package.json, leading to unauthorized package republishing and reputation inflation.
You can use Vulert to monitor your application for vulnerabilities. By utilizing the package-lock.json file, Vulert can alert you in real-time about any open-source vulnerabilities.
To prevent similar vulnerabilities, regularly audit your dependencies and use tools like Vulert to monitor for known vulnerabilities in your packages.
If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.
Detailed information can be found in the vulnerability report on the official npm registry or through security advisories related to the package.
