Malicious Code Injection in munir-terd-ytu Package - npm Vulnerability

munir-terd-ytu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160944: Malicious code in munir-terd-ytu (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 munir-terd-ytu 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 distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the automatic generation of derivative packages.

Vulnerability Detail

The vulnerability in the munir-terd-ytu package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry by continuously republishing variants of the package, which can lead to security risks for developers who unknowingly use these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities.

How To Fix

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

npm uninstall munir-terd-ytu

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 munir-terd-ytu package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities.

Conclusion

The munir-terd-ytu package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for munir-terd-ytu →

Share this vulnerability

FAQ

The munir-terd-ytu package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the munir-terd-ytu package immediately and review your project's dependencies for any other potentially compromised packages.

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

How To Fix

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

npm uninstall munir-terd-ytu

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