Malicious Code Injection in vera-gaplek74-breki Package - npm Vulnerability

vera-gaplek74-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75956: Malicious code in vera-gaplek74-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The vera-gaplek74-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, to remove private flags and change version numbers, leading to potential misuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the vera-gaplek74-breki package, which contains scripts that automate the generation and publication of derivative packages. This behavior can lead to the proliferation of unwanted packages in the npm registry, compromising the integrity of the ecosystem. The malicious payload alters package.json files, which can result in unintended exposure of sensitive information and disrupt the normal functioning of applications relying on this package.

How To Fix

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

npm uninstall vera-gaplek74-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 vera-gaplek74-breki package and replace it with a trusted alternative. Ensure that your package-lock.json is updated to reflect this change. You can also use the following command to audit your dependencies for vulnerabilities: 'npm audit'.

Conclusion

The vera-gaplek74-breki package poses a significant risk due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to ensure the security and integrity of your applications.

See every vulnerability recorded for vera-gaplek74-breki →

Share this vulnerability

FAQ

The vera-gaplek74-breki package is an npm package identified as malicious, designed to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the exposure of sensitive information and the pollution of the npm registry, potentially affecting the stability and security of your application.

You should uninstall the vera-gaplek74-breki package immediately and audit your dependencies to ensure no other malicious packages are present.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall vera-gaplek74-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