Malicious Code Injection in iwan-botok62-breki Package

iwan-botok62-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73564: Malicious code in iwan-botok62-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 iwan-botok62-breki package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. It modifies critical files such as package.json, removing private flags and altering version numbers, which can lead to significant security risks for developers using this package.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the iwan-botok62-breki package, which is part of a broader scheme to manipulate the npm registry. The package contains scripts that automatically publish variants of itself with altered names and configurations, effectively polluting the npm registry. This behavior can lead to unauthorized access to sensitive information, as well as the potential for developers to unknowingly incorporate malicious code into their applications.

How To Fix

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

npm uninstall iwan-botok62-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 iwan-botok62-breki package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The iwan-botok62-breki package poses a significant security risk due to its malicious code that alters package configurations and publishes unauthorized variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for iwan-botok62-breki →

Share this vulnerability

FAQ

It is a malicious npm package that is part of a scheme to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file and the introduction of malicious code into your application.

You should uninstall the iwan-botok62-breki package immediately and monitor your application for any unusual behavior.

Yes, regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

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 iwan-botok62-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