Malicious Code Injection in munir-teaars-sdaa: A Threat to npm Ecosystem

munir-teaars-sdaa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160930: Malicious code in munir-teaars-sdaa (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 package 'munir-teaars-sdaa' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is typically used for publishing JavaScript packages. However, it has been identified as containing malicious code that compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'munir-teaars-sdaa' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants to pollute the npm registry. This behavior not only inflates developer reputation scores for token rewards but also poses a significant risk of dependency confusion and potential exploitation by malicious actors.

How To Fix

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

npm uninstall munir-teaars-sdaa

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 workaround, you can temporarily prevent the installation of this package by using npm's package-lock.json to lock your dependencies. Additionally, consider using the following command to audit your project for vulnerabilities: npm audit.

Conclusion

The 'munir-teaars-sdaa' package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities.

See every vulnerability recorded for munir-teaars-sdaa →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and republishes variants to the npm registry, compromising the integrity of the ecosystem.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Remove the 'munir-teaars-sdaa' package from your project and update your dependencies to ensure you are not using any compromised versions.

While specific exploits have not been detailed, the malicious behavior of the package can lead to dependency confusion and potential exploitation by attackers.

Regularly audit your dependencies using tools like npm audit and stay informed about vulnerabilities in the packages you use.

How To Fix

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

npm uninstall munir-teaars-sdaa

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