Malicious Code Injection in juris-qeuspss-ur Package: A Threat to npm Users

juris-qeuspss-ur Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157125: Malicious code in juris-qeuspss-ur (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The juris-qeuspss-ur package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability originates from the juris-qeuspss-ur package being part of a malicious campaign associated with the tea.xyz token reward scheme. The package contains scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to security threats.

How To Fix

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

npm uninstall juris-qeuspss-ur

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 workaround, avoid using the juris-qeuspss-ur package and consider using alternative packages that provide similar functionality without the associated risks. Always review package dependencies and their sources before installation.

Conclusion

The juris-qeuspss-ur package poses a significant security threat due to its malicious code and the potential for dependency pollution. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed about package security is essential for maintaining the integrity of software applications.

See every vulnerability recorded for juris-qeuspss-ur →

Share this vulnerability

FAQ

The juris-qeuspss-ur package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

If your application uses the juris-qeuspss-ur package, it may be exposed to security risks, including the potential for malicious code execution and dependency pollution.

You should uninstall the juris-qeuspss-ur package immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

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

How To Fix

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

npm uninstall juris-qeuspss-ur

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