Malicious Code Injection in joni-nasi56-breki Package: A Threat to npm Ecosystem

joni-nasi56-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73820: Malicious code in joni-nasi56-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 joni-nasi56-breki package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. The primary functionality of this package is to inflate developer reputation scores for token rewards, but it does so through harmful practices that compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the joni-nasi56-breki package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, leading to pollution of the npm registry. This behavior not only affects the reputation of legitimate developers but also poses security risks to applications relying on these packages.

How To Fix

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

npm uninstall joni-nasi56-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 this malicious package by using npm's package-lock.json to monitor dependencies. You can also utilize the following command to audit your project for vulnerabilities: npm audit.

Conclusion

The joni-nasi56-breki package poses a significant threat to the npm ecosystem through its malicious activities. It is essential for developers to be vigilant and take necessary actions to mitigate the risks associated with this vulnerability. By removing the package and utilizing tools like Vulert, developers can better protect their applications from such threats.

See every vulnerability recorded for joni-nasi56-breki →

Share this vulnerability

FAQ

The joni-nasi56-breki package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and affecting the integrity of your application.

You should remove the joni-nasi56-breki package from your project and update to a secure alternative if available.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, 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 joni-nasi56-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