Malicious Code Injection in joko-lutis20-breki Package

joko-lutis20-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73734: Malicious code in joko-lutis20-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 joko-lutis20-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 compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's 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 affecting other developers and users relying on legitimate packages. The malicious scripts included in the package are designed to automate these processes, making it difficult to track and mitigate the issue.

How To Fix

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

npm uninstall joko-lutis20-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, avoid using the joko-lutis20-breki package and monitor your project for any dependencies that may have inadvertently included it. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities. To check if your application is affected by this vulnerability, you can visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The joko-lutis20-breki package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for joko-lutis20-breki →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to pollution of the npm registry and potential security risks.

You should uninstall the package immediately using the command npm uninstall joko-lutis20-breki and ensure that you do not reinstall it.

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

You can check if your application is affected by visiting the Vulert playground at Vulert Scanner, where you can analyze your dependencies without signing up.

How To Fix

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

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