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

jurss-a1rea-as Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157131: Malicious code in jurss-a1rea-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The jurss-a1rea-as package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various functionalities within applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the jurss-a1rea-as package stems from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The origin of this vulnerability is linked to automated scripts designed to exploit the npm ecosystem for malicious gain.

How To Fix

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

npm uninstall jurss-a1rea-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, you can avoid using the jurss-a1rea-as package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The jurss-a1rea-as package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.

See every vulnerability recorded for jurss-a1rea-as →

Share this vulnerability

FAQ

The jurss-a1rea-as package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

This vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially exposing your application to further risks.

You should uninstall the jurss-a1rea-as package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in your software.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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