Malicious Code Injection in jurss-gdasa-a1s: A Threat to npm Packages
Summary
MAL-2025-157183: Malicious code in jurss-gdasa-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-gdasa-a1s' is part of a larger ecosystem on npm, which is a platform for sharing and managing JavaScript packages. This particular package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary functionality appears to be linked to generating and publishing derivative packages, but it has been compromised to execute harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'jurss-gdasa-a1s' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores fraudulently and pollute the npm registry with numerous derivative packages. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jurss-gdasa-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 this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include 'jurss-gdasa-a1s' in its dependencies. You can also use the following command to uninstall it if it's already installed: 'npm uninstall jurss-gdasa-a1s'.
Conclusion
The 'jurss-gdasa-a1s' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your application.
See every vulnerability recorded for jurss-gdasa-a1s →
FAQ
The impact includes potential exposure to malicious code that can alter your project's package metadata and inflate reputation scores fraudulently.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using 'npm uninstall jurss-gdasa-a1s' and check for any other affected packages.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
Signs include unexpected changes in your package.json file, unusual package versions, or the presence of unknown packages in your project.
