Malicious Code Injection in munir-terd-tessdrb: A Threat to npm Users

munir-terd-tessdrb Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160939: Malicious code in munir-terd-tessdrb (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 package 'munir-terd-tessdrb' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate npm's package registry by automatically generating and publishing derivative packages. Its functionality is compromised due to the presence of malicious scripts that can alter package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in 'munir-terd-tessdrb' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to identify and mitigate the threat.

How To Fix

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

npm uninstall munir-terd-tessdrb

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 'munir-terd-tessdrb' package from your project by executing: 'npm uninstall munir-terd-tessdrb'. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code directly.

Conclusion

The 'munir-terd-tessdrb' package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the registry. It is essential to take immediate action by updating or uninstalling the package and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for munir-terd-tessdrb →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that alters package metadata and floods the npm registry with derivative packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Using this package can lead to the pollution of the npm registry, compromise the integrity of your application, and inflate developer reputation scores fraudulently.

Regularly updating your packages, using vulnerability scanning tools like Vulert, and monitoring package dependencies can help prevent such vulnerabilities.

If you have installed this package, you should uninstall it immediately and check for any updates or patches that may be available.

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 munir-terd-tessdrb

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