Malicious Code Vulnerability in jurss-zsa-as Package

jurss-zsa-as Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157228: Malicious code in jurss-zsa-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-zsa-as package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically include scripts that automate the generation and publication of derivative packages, aimed at inflating developer reputation scores for token rewards. The presence of such malicious code poses a significant risk to developers and users relying on this package.

Vulnerability Detail

The vulnerability in the jurss-zsa-as package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent applications. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for nefarious purposes.

How To Fix

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

npm uninstall jurss-zsa-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 workaround, consider using a package-lock.json file to lock your dependencies and prevent the installation of the vulnerable package. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access or installation.

Conclusion

The jurss-zsa-as package contains a significant vulnerability that can compromise the integrity of applications relying on it. It is crucial to uninstall this package and monitor your dependencies for any malicious activity. Utilizing tools like Vulert can help ensure your application remains secure.

See every vulnerability recorded for jurss-zsa-as →

Share this vulnerability

FAQ

The jurss-zsa-as package is an npm package that has been associated with malicious activities, specifically related to the tea.xyz token reward campaign.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

You should uninstall the jurss-zsa-as package immediately using the command: npm uninstall jurss-zsa-as.

Yes, you can use Vulert to monitor your application for open-source vulnerabilities in real-time using just your package-lock.json file.

Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

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