Malicious Code Injection in jurss-dsf-as Package - npm Vulnerability

jurss-dsf-as Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157153: Malicious code in jurss-dsf-as (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-dsf-as package is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in 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 for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious scripts within the jurss-dsf-as package. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall jurss-dsf-as

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, you can avoid using the jurss-dsf-as package and any other packages that may have been published as part of the same malicious campaign. Monitor your package.json and package-lock.json files for any unauthorized changes.

Conclusion

The jurss-dsf-as package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to safeguard your projects.

See every vulnerability recorded for jurss-dsf-as →

Share this vulnerability

FAQ

The jurss-dsf-as package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of compromised packages.

Using the jurss-dsf-as package can lead to unauthorized modifications in your project, potentially compromising its security and integrity.

You should immediately uninstall the jurss-dsf-as package using the command npm uninstall jurss-dsf-as and review your project for any other compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground at Vulert Scanner without needing to sign up.

There are no patches available for the jurss-dsf-as package as it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall jurss-dsf-as

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