Malicious Code Injection in jurss-gasd-13as Package: npm Vulnerability Summary

jurss-gasd-13as Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157175: Malicious code in jurss-gasd-13as (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The jurss-gasd-13as package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify the package.json file, removing private flags and altering version numbers, which can lead to significant security risks in the npm ecosystem.

Vulnerability Detail

The vulnerability in the jurss-gasd-13as package originates from its design to execute autopublish scripts that generate and publish numerous derivative packages. This behavior not only pollutes the npm registry but also compromises the integrity of the developer's project by modifying critical files like package.json. The ramifications include potential exposure to further malicious code, loss of control over package versions, and damage to the developer's reputation. The technical aspects involve the removal of private flags and the generation of random package names, which can confuse dependency management.

How To Fix

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

npm uninstall jurss-gasd-13as

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 prevent the execution of the autopublish scripts by setting stricter permissions on your npm environment or using a package manager that allows for more controlled installations. Additionally, you can monitor your dependencies using tools like Vulert to receive real-time alerts for any open-source vulnerabilities.

Conclusion

The jurss-gasd-13as package poses a significant risk due to its malicious code that modifies essential project files and publishes derivative packages. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for jurss-gasd-13as →

Share this vulnerability

FAQ

The jurss-gasd-13as package is a malicious npm package that is part of a campaign to inflate developer reputation scores by generating and publishing numerous derivative packages.

This vulnerability can compromise your project's integrity by modifying critical files and potentially exposing your project to further malicious code.

You should uninstall the jurss-gasd-13as package immediately and check your package.json and package-lock.json files for any references to it.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall jurss-gasd-13as

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