Malicious Code Injection in jaja-jus19-breki: A Threat to npm Packages

jaja-jus19-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73628: Malicious code in jaja-jus19-breki (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package jaja-jus19-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous variants with random names.

Vulnerability Detail

The vulnerability in jaja-jus19-breki originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially compromise the integrity of other packages relying on it.

How To Fix

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

npm uninstall jaja-jus19-breki

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 jaja-jus19-breki package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities without requiring access to the code or installation.

Conclusion

The jaja-jus19-breki package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and alerting for such vulnerabilities in real-time.

See every vulnerability recorded for jaja-jus19-breki →

Share this vulnerability

FAQ

jaja-jus19-breki is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting your project's reliability.

You should uninstall the package immediately using the command: npm uninstall jaja-jus19-breki.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall jaja-jus19-breki

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