Malicious Code Injection in jurss-aseaspa-a1s: A Threat to npm Packages
Summary
MAL-2025-157144: Malicious code in jurss-aseaspa-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 package jurss-aseaspa-a1s is part of a broader campaign targeting npm repositories, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores within the npm ecosystem. Its functionality revolves around creating random package names and republishing them, which can clutter the npm registry and pose risks to users relying on these packages.
Vulnerability Detail
The vulnerability in jurss-aseaspa-a1s stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. This behavior allows the package to generate random names, primarily themed around Indonesian culture, and continuously republish these variants. The origin of this vulnerability is linked to a campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers who may unknowingly incorporate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jurss-aseaspa-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 workaround, you can avoid using the jurss-aseaspa-a1s package and any other packages that may be part of the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit or Vulert to identify and mitigate risks from malicious packages.
Conclusion
The jurss-aseaspa-a1s package poses a significant threat to npm users due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects.
See every vulnerability recorded for jurss-aseaspa-a1s →
FAQ
jurss-aseaspa-a1s is an npm package involved in a malicious campaign that automates the creation and publication of derivative packages.
If included in your project, this package can lead to security risks, including the potential for your application to be compromised or polluted with unwanted packages.
You should uninstall the jurss-aseaspa-a1s package immediately and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
