Malicious Code Injection in maya-tek47-breki Package - npm Vulnerability

maya-tek47-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74442: Malicious code in maya-tek47-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 maya-tek47-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages designed to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that employs malicious scripts to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as they may introduce vulnerabilities into their applications.

How To Fix

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

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

Conclusion

The maya-tek47-breki package poses a significant security risk due to its malicious code designed to manipulate npm registry and developer reputation. 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 maya-tek47-breki →

Share this vulnerability

FAQ

The maya-tek47-breki package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

Using the maya-tek47-breki package can introduce security risks, as it modifies your package.json and can lead to the installation of other malicious packages.

You should uninstall the maya-tek47-breki package immediately and check your project for any other affected dependencies.

You can use 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 signing up.

How To Fix

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

npm uninstall maya-tek47-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