Malicious Code Injection in wati-jengkol91-breki Package

wati-jengkol91-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76118: Malicious code in wati-jengkol91-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 wati-jengkol91-breki package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity.

Vulnerability Detail

The vulnerability in the wati-jengkol91-breki package originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall wati-jengkol91-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 remove the wati-jengkol91-breki package from your project by executing the following command: npm uninstall wati-jengkol91-breki. This will prevent the malicious code from executing in your environment until a secure version is available.

Conclusion

The wati-jengkol91-breki package has been identified as containing malicious code that poses significant risks to projects using it. It is crucial to monitor for updates and consider removing the package until a secure version is available. Utilizing tools like Vulert can help in identifying vulnerabilities in your project efficiently.

See every vulnerability recorded for wati-jengkol91-breki →

Share this vulnerability

FAQ

The wati-jengkol91-breki package is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially exposing sensitive data and affecting the integrity of your application.

It is advisable to check the npm registry for any patched versions of the wati-jengkol91-breki package. If available, updating to the latest version will mitigate the risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

If immediate updates are not possible, consider uninstalling the package to prevent any malicious code from executing in your environment.

How To Fix

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

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