Malicious Code Injection in joni-toge16-breki: A Threat to npm Packages
Summary
MAL-2025-73840: Malicious code in joni-toge16-breki (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package joni-toge16-breki is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The package's primary function appears to be tied to the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in joni-toge16-breki stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is orchestrated through scripts that continuously republish variants of the package, thereby compromising the integrity of the npm registry and potentially affecting developers who rely on these packages. The malicious payload can lead to unauthorized access to sensitive information and can damage the reputation of legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joni-toge16-brekiIf 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 joni-toge16-breki package in your projects. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The joni-toge16-breki package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to be vigilant and remove any affected packages from their projects to maintain security and integrity.
See every vulnerability recorded for joni-toge16-breki →
FAQ
joni-toge16-breki is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the joni-toge16-breki package immediately using 'npm uninstall joni-toge16-breki' to mitigate any risks.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
