Malicious Code Detected in muklis-25: A Threat to npm Users

muklis-25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160809: Malicious code in muklis-25 (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 muklis-25 is part of a broader campaign targeting npm users, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's ecosystem by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in muklis-25 arises from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm platform.

How To Fix

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

npm uninstall muklis-25

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 measure, you can avoid using the muklis-25 package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to identify and remove any malicious packages.

Conclusion

The discovery of malicious code in the muklis-25 package highlights the importance of vigilance in the npm ecosystem. Developers should take proactive steps to secure their projects by removing compromised packages and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for muklis-25 →

Share this vulnerability

FAQ

Muklis-25 is an npm package that has been identified as malicious, designed to manipulate the npm ecosystem for token reward purposes.

The package can compromise your project's integrity by modifying essential files and introducing potentially harmful code.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should immediately uninstall the package using npm uninstall muklis-25 and review your other dependencies for any related vulnerabilities.

Regularly audit your dependencies, use trusted packages, and keep your software updated to minimize the risk of vulnerabilities.

How To Fix

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

npm uninstall muklis-25

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