Malicious Code Injection in wati-kue35-breki Package

wati-kue35-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76126: Malicious code in wati-kue35-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wati-kue35-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of this package is to serve as a token reward mechanism for the tea.xyz protocol, but it has been compromised to perform harmful actions.

Vulnerability Detail

The vulnerability originates from the wati-kue35-breki package, which contains malicious code designed to manipulate the npm registry. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, effectively polluting the npm ecosystem. The malicious payload can lead to reputation inflation for developers and may expose users to further security risks by allowing unauthorized access to sensitive data.

How To Fix

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

npm uninstall wati-kue35-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 wati-kue35-breki package and any other packages that may be linked to the tea.xyz token reward campaign. Regularly monitor your package dependencies and remove any suspicious packages.

Conclusion

The wati-kue35-breki package poses a significant security risk due to its malicious code that manipulates the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for wati-kue35-breki →

Share this vulnerability

FAQ

The wati-kue35-breki package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and reputation inflation.

You should uninstall the wati-kue35-breki package immediately and run 'npm audit fix' to ensure your project is secure.

You can use tools like Vulert, which monitors your package-lock.json file 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 signing up.

How To Fix

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

npm uninstall wati-kue35-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