Malicious Code Injection in jurss-zas-durs Package - npm Vulnerability

jurss-zas-durs Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157225: Malicious code in jurss-zas-durs (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The jurss-zas-durs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the jurss-zas-durs package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby allowing the package to continuously republish variants. The origin of this issue is linked to the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms for malicious purposes. The ramifications include potential security risks for developers and users who may inadvertently install these compromised packages, leading to further exploitation.

How To Fix

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

npm uninstall jurss-zas-durs

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 measure, avoid using the jurss-zas-durs package and any packages that depend on it. Regularly monitor your package-lock.json file for any unauthorized changes or additions, and consider using tools like Vulert to track vulnerabilities in your dependencies.

Conclusion

The jurss-zas-durs package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is essential to remove this package and monitor your dependencies for vulnerabilities to ensure the security of your projects.

See every vulnerability recorded for jurss-zas-durs →

Share this vulnerability

FAQ

The jurss-zas-durs package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the installation of compromised packages, posing security risks to your project.

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

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

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall jurss-zas-durs

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