Malicious Code Vulnerability in async-encrypt-void-user-upsilon Package
Summary
MAL-2025-185617: Malicious code in async-encrypt-void-user-upsilon (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 async-encrypt-void-user-upsilon package is part of the npm ecosystem, often utilized for asynchronous encryption tasks. 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 the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward system. It includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall async-encrypt-void-user-upsilonIf 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 async-encrypt-void-user-upsilon package and replace it with a trusted alternative for asynchronous encryption tasks. Always verify the integrity and source of packages before including them in your project.
Conclusion
The async-encrypt-void-user-upsilon package poses a significant risk due to its involvement in a malicious campaign that manipulates the npm registry. It is crucial to remove this package from your projects and to stay vigilant about the packages you use. Utilizing tools like Vulert can help you monitor for vulnerabilities effectively.
See every vulnerability recorded for async-encrypt-void-user-upsilon →
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, compromising the integrity of your dependencies and potentially introducing security risks.
You should uninstall the async-encrypt-void-user-upsilon package immediately and replace it with a trusted alternative.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
