Malicious Code Injection in jurss-za-as Package: A Threat to npm Users
Summary
MAL-2025-157213: Malicious code in jurss-za-as (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-za-as package is part of a broader ecosystem within npm that has been exploited for malicious purposes. This package is linked to the tea.xyz token reward campaign, which has been associated with a surge of similar malicious packages. These packages typically aim to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the jurss-za-as package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages. The origin of this vulnerability is linked to the automated scripts that are part of the tea.xyz token reward campaign, which flood the npm ecosystem with malicious content.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jurss-za-asIf 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 manually check your package-lock.json file for any references to jurss-za-as and remove it. After that, run the following command to clean up your dependencies: npm prune.
Conclusion
The jurss-za-as package poses a significant threat to npm users due to its malicious behavior aimed at manipulating package metadata and inflating developer reputation scores. It is essential to remove this package from your projects and monitor for any similar vulnerabilities to maintain the integrity of your development environment.
See every vulnerability recorded for jurss-za-as →
FAQ
The jurss-za-as package is an npm package that has been identified as malicious, linked to a campaign that aims to inflate developer reputation scores through automated publishing.
If your project uses the jurss-za-as package, it may be at risk of having its package.json modified, leading to potential security vulnerabilities and pollution of the npm registry.
You should immediately remove the jurss-za-as package from your project and check for any unauthorized changes in your package.json file.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
