Malicious Code Injection in jurss-sdfud-as Package: A Threat to npm Ecosystem

jurss-sdfud-as Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157210: Malicious code in jurss-sdfud-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The jurss-sdfud-as package is part of a malicious campaign targeting the npm ecosystem, specifically designed to exploit developer reputation systems. This package, like others in the tea.xyz token reward scheme, contains scripts that automate the generation and publication of derivative packages with randomized names. Its primary function is to inflate reputation scores for token rewards, but it poses significant risks to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the jurss-sdfud-as package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior not only compromises the security of the npm ecosystem but also misleads developers and users regarding the authenticity and safety of packages.

How To Fix

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

npm uninstall jurss-sdfud-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

Currently, the best workaround is to avoid using the jurss-sdfud-as package altogether. If it is already in your project, uninstall it immediately and monitor your dependencies for any similar malicious packages.

Conclusion

The jurss-sdfud-as package represents a significant threat to the npm ecosystem due to its malicious intent and actions. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate risks associated with this package.

See every vulnerability recorded for jurss-sdfud-as →

Share this vulnerability

FAQ

The jurss-sdfud-as package is a malicious npm package designed to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the pollution of your project's dependencies, potentially introducing other malicious packages and compromising the security of your application.

You should uninstall the jurss-sdfud-as package immediately and check your package-lock.json for any lingering references to it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.

Yes, be vigilant for other packages that may be part of the tea.xyz token reward campaign or exhibit similar malicious behaviors. Regularly audit your dependencies.

How To Fix

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

npm uninstall jurss-sdfud-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