Malicious Code Injection in jurss-gsd-a3s Package: A Threat to npm Users
Summary
MAL-2025-157191: Malicious code in jurss-gsd-a3s (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The jurss-gsd-a3s package is part of the npm ecosystem, designed to facilitate various functionalities within JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package, like others in the campaign, employs scripts that automatically generate and publish variants with altered names and metadata, aiming to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability stems from the malicious nature of the jurss-gsd-a3s package, which modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jurss-gsd-a3sIf 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-gsd-a3s package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The jurss-gsd-a3s package poses a significant threat to npm users due to its malicious code that alters package metadata and inflates developer reputation scores. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity and security of your projects.
See every vulnerability recorded for jurss-gsd-a3s →
FAQ
jurss-gsd-a3s is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
Using the jurss-gsd-a3s package can compromise your project's integrity, potentially leading to security breaches and affecting your reputation as a developer.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without requiring signup.
If you have used the jurss-gsd-a3s package, it is crucial to uninstall it immediately and review your project's dependencies for any other potentially malicious packages.
Yes, tools like Vulert can help you monitor your package-lock.json file for vulnerabilities in real-time, ensuring your application remains secure.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
