Malicious Code Injection in joni-klanting46-breki: A Threat to npm Packages

joni-klanting46-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73806: Malicious code in joni-klanting46-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 package joni-klanting46-breki is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. It aims to inflate developer reputation scores for rewards associated with the tea protocol, making it a potential vector for malicious activities.

Vulnerability Detail

The vulnerability in joni-klanting46-breki stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and compromise the integrity of the npm ecosystem.

How To Fix

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

npm uninstall joni-klanting46-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 joni-klanting46-breki package and replace it with a trusted alternative. Always validate the packages you include in your project to ensure they do not contain malicious code.

Conclusion

The joni-klanting46-breki package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant about the packages they use and to employ tools like Vulert for monitoring vulnerabilities. Taking immediate action to remove affected packages and regularly updating dependencies can help maintain the security of your projects.

See every vulnerability recorded for joni-klanting46-breki →

Share this vulnerability

FAQ

The joni-klanting46-breki package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

This vulnerability can compromise the integrity of your project by introducing malicious code and affecting your developer reputation.

You should uninstall the joni-klanting46-breki package immediately and review your project for any other potentially malicious dependencies.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities using just the package-lock.json file, providing real-time alerts.

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

How To Fix

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

npm uninstall joni-klanting46-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