Malicious Code in async-development-jovian-jwt: A Threat to npm Packages
Summary
MAL-2025-139623: Malicious code in async-development-jovian-jwt (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 'async-development-jovian-jwt' is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate asynchronous operations in applications. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that have randomized names, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has been known to introduce malicious scripts into npm packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall async-development-jovian-jwtIf 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 measure, you can avoid using the 'async-development-jovian-jwt' 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 any open-source vulnerabilities.
Conclusion
The 'async-development-jovian-jwt' package poses a significant risk due to its association with malicious activities aimed at manipulating the npm registry. Developers are urged to remove this package and monitor their projects for vulnerabilities using tools like Vulert to maintain the integrity of their applications.
See every vulnerability recorded for async-development-jovian-jwt →
FAQ
The package is part of a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert to analyze your package-lock.json file for vulnerabilities without needing to install any software.
Using this package can lead to security risks, including the pollution of the npm registry and potential exploitation of your application.
Regularly monitor your dependencies for vulnerabilities and consider using tools like Vulert for real-time alerts.
Remove the package immediately and look for alternatives. Ensure to check for any updates or patches that may address the vulnerability.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.