Malicious Code Injection in jurss-gsswa-a1s Package: A Threat to npm Ecosystem
Summary
MAL-2025-157203: Malicious code in jurss-gsswa-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-gsswa-a1s package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the jurss-gsswa-a1s package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially affecting any application that relies on them. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit the npm ecosystem for fraudulent gains.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jurss-gsswa-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 prevent the installation of the jurss-gsswa-a1s package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include this package in its dependencies. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json for any open-source vulnerabilities.
Conclusion
The jurss-gsswa-a1s package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for jurss-gsswa-a1s →
FAQ
The jurss-gsswa-a1s package is an npm package associated with a token reward campaign that has been identified as malicious.
This vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.
You should immediately remove the jurss-gsswa-a1s package from your project and monitor for any updates or patches.
Yes, you can use tools like Vulert to monitor your dependencies for vulnerabilities in real-time and ensure that you are alerted to any issues.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
