Malicious Code Injection in jurss-adssdsea-a1s Package - npm Vulnerability

jurss-adssdsea-a1s Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157133: Malicious code in jurss-adssdsea-a1s (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-adssdsea-a1s package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior compromises the integrity of the npm registry and can lead to further exploitation.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the jurss-adssdsea-a1s package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The malicious payload can also affect the reputation of legitimate developers and disrupt the ecosystem.

How To Fix

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

npm uninstall jurss-adssdsea-a1s

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, avoid using the jurss-adssdsea-a1s package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using the command: npm audit to identify vulnerabilities.

Conclusion

The jurss-adssdsea-a1s package poses a significant threat to the integrity of the npm ecosystem. By understanding the nature of this vulnerability and taking proactive steps to remove the package and monitor your dependencies, you can protect your projects from potential exploitation.

See every vulnerability recorded for jurss-adssdsea-a1s →

Share this vulnerability

FAQ

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

This vulnerability can lead to the installation of compromised packages, potentially exposing your project to security risks and affecting your reputation as a developer.

You should immediately uninstall the jurss-adssdsea-a1s package and check your project for any other malicious packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools to monitor for vulnerabilities.

How To Fix

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

npm uninstall jurss-adssdsea-a1s

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