Malicious Code Exploit in Joko-Tahu99-Breki Package: npm Vulnerability Overview

joko-tahu99-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73784: Malicious code in joko-tahu99-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'joko-tahu99-breki' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package configurations and republishes variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This malicious behavior leads to the generation of random package names, which can clutter the npm registry and potentially compromise the integrity of the ecosystem. The continuous republishing of these variants can mislead developers and users, affecting their trust in legitimate packages.

How To Fix

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

npm uninstall joko-tahu99-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 prevent the installation of the 'joko-tahu99-breki' package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package in any of its dependencies.

Conclusion

The 'joko-tahu99-breki' package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to remove this package from their projects and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for joko-tahu99-breki →

Share this vulnerability

FAQ

The 'joko-tahu99-breki' package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting developer trust.

If you have installed the 'joko-tahu99-breki' package, you should uninstall it immediately using 'npm uninstall joko-tahu99-breki' and check for any affected dependencies.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

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

How To Fix

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

npm uninstall joko-tahu99-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