Critical Malicious Code Vulnerability in matka (npm) - MAL-2025-6104

matka Updated 02 Oct 2025

Summary

12/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6104: Malicious code in matka (npm). Affects matka versions >= 99.99.99. 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 'matka' package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its recent vulnerability has raised concerns. The package has been found to communicate with a domain associated with malicious activity, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability identified as MAL-2025-6104 originates from the 'matka' package's communication with a domain linked to malicious activities. This could lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The malicious code can compromise the integrity of applications that rely on this package, making it critical for developers to address this issue promptly.

How To Fix

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

npm uninstall matka

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 'matka' package from your project until a secure version is released. This can be done using the command: 'npm uninstall matka'. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The 'matka' package has a critical vulnerability that allows communication with a malicious domain, posing significant risks to applications. It is crucial for developers to update the package or implement workarounds to protect their systems. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for matka →

Share this vulnerability

FAQ

The 'matka' package is an npm library used for various functionalities in JavaScript applications, but its specific use cases may vary.

The risks include unauthorized data access, potential data breaches, and exploitation of the affected systems due to malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If a patched version is available, you can update the package using 'npm update matka' to secure your application.

As a temporary measure, consider uninstalling the 'matka' package using 'npm uninstall matka' or using an alternative package until a secure version is released.

How To Fix

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

npm uninstall matka

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