Malicious Code Injection in jurss-zss-drs Package: A Threat to npm Users

jurss-zss-drs Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157231: Malicious code in jurss-zss-drs (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-zss-drs package is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in token reward programs. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata. Its primary function is to inflate developer reputation scores for rewards, but this comes at the cost of security and integrity within the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the jurss-zss-drs package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry with numerous derivative packages, potentially leading to confusion and misuse by developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with such malicious packages.

How To Fix

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

npm uninstall jurss-zss-drs

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-zss-drs package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project's dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The jurss-zss-drs package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for jurss-zss-drs →

Share this vulnerability

FAQ

The jurss-zss-drs package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to confusion and potential security risks.

You should uninstall the jurss-zss-drs package immediately using npm uninstall jurss-zss-drs and check for any other affected packages in your project.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall jurss-zss-drs

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