Malicious Code Vulnerability in actual_koi-appteadev Package
Summary
MAL-2025-99103: Malicious code in actual_koi-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 actual_koi-appteadev package is part of the npm ecosystem, primarily used for developing applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the actual_koi-appteadev package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The malicious payload can inflate developer reputation scores fraudulently, posing a risk to the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall actual_koi-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 actual_koi-appteadev package entirely and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The actual_koi-appteadev package contains a serious vulnerability that can compromise the integrity of applications relying on it. It is crucial to remove this package and monitor for any updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.
See every vulnerability recorded for actual_koi-appteadev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that depend on the actual_koi-appteadev package.
You should remove the actual_koi-appteadev package from your project and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
