Malicious Code Injection in jurss-aseaspsa-a1s Package: npm Vulnerability Overview
Summary
MAL-2025-157145: Malicious code in jurss-aseaspsa-a1s (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 jurss-aseaspsa-a1s package is part of a broader campaign targeting the npm ecosystem, specifically designed to exploit developer reputation systems. It is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous malicious packages that manipulate the npm registry. These packages often include scripts that automate the generation and publication of derivative packages, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the jurss-aseaspsa-a1s package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jurss-aseaspsa-a1sIf 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 jurss-aseaspsa-a1s package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.
Conclusion
The jurss-aseaspsa-a1s package poses a significant risk to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry with derivative packages. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for jurss-aseaspsa-a1s →
FAQ
The jurss-aseaspsa-a1s package is a malicious npm package that is part of a campaign to exploit developer reputation systems by flooding the npm registry with derivative packages.
This vulnerability can lead to dependency confusion, where your application may inadvertently rely on malicious packages, potentially compromising security and functionality.
You should immediately uninstall the jurss-aseaspsa-a1s package and audit your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Yes, tools like npm audit and Vulert can help identify and alert you to vulnerabilities in your dependencies, ensuring your application remains secure.
