Malicious Code Injection in jurss-gdassa-a1s Package: A Threat to npm Ecosystem

jurss-gdassa-a1s Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157184: Malicious code in jurss-gdassa-a1s (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The jurss-gdassa-a1s package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the ecosystem, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to generate and distribute harmful code. The package is associated with the tea.xyz token reward scheme, which aims to inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the jurss-gdassa-a1s package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly integrate 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-gdassa-a1s

If 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-gdassa-a1s package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to identify and remove any potentially harmful packages.

Conclusion

The jurss-gdassa-a1s package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing harmful variants. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects against such threats.

See every vulnerability recorded for jurss-gdassa-a1s →

Share this vulnerability

FAQ

The jurss-gdassa-a1s package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

If you have installed the jurss-gdassa-a1s package, you should uninstall it immediately using the command: npm uninstall jurss-gdassa-a1s.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring that you are alerted to any potential threats.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall jurss-gdassa-a1s

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback