Malicious Code Injection in jurss-gad-14s Package: A Threat to npm Ecosystem

jurss-gad-14s Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157167: Malicious code in jurss-gad-14s (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The jurss-gad-14s package is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the jurss-gad-14s package stems from its association with malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to create a multitude of derivative packages, thereby affecting the integrity of the npm ecosystem.

How To Fix

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

npm uninstall jurss-gad-14s

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 installation of the jurss-gad-14s package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your dependencies without requiring code access or installation.

Conclusion

The jurss-gad-14s 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 stay vigilant about updates. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for jurss-gad-14s →

Share this vulnerability

FAQ

The jurss-gad-14s package is part of a malicious campaign that automates the creation and publication of npm packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should remove the jurss-gad-14s package from your project and monitor for any updates or patches.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, ensuring real-time updates on potential threats.

How To Fix

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

npm uninstall jurss-gad-14s

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