Malicious Code Injection in verify-aysali-aisai Package
Summary
MAL-2025-170426: Malicious code in verify-aysali-aisai (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 verify-aysali-aisai package is part of the npm ecosystem, often used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for the tea protocol token rewards. The continuous republishing of these variants leads to pollution of the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-aysali-aisaiIf 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 workaround, you can avoid using the verify-aysali-aisai package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The verify-aysali-aisai package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for verify-aysali-aisai →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should remove the verify-aysali-aisai package from your project immediately and monitor for any updates or patches.
You can use Vulert, which allows you to monitor your package-lock.json for vulnerabilities without needing to install any software.
Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without any signup.
