Malicious Code Injection in vera-jengkol86-breki: A Threat to npm Users

vera-jengkol86-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75960: Malicious code in vera-jengkol86-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 package 'vera-jengkol86-breki' 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 aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability in 'vera-jengkol86-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 not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The malicious payload is designed to continuously republish variants, further exacerbating the problem.

How To Fix

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

npm uninstall vera-jengkol86-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 your dependencies. Ensure that your project does not include 'vera-jengkol86-breki' in the package.json file. You can also use the following command to audit your project for vulnerabilities: npm audit.

Conclusion

The 'vera-jengkol86-breki' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and stay informed about potential vulnerabilities in their dependencies. Utilizing tools like Vulert can help in maintaining the security of your projects.

See every vulnerability recorded for vera-jengkol86-breki →

Share this vulnerability

FAQ

'vera-jengkol86-breki' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should remove 'vera-jengkol86-breki' from your project and monitor for any updates or patches.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json.

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 vera-jengkol86-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