Malicious Code Injection in inherent_marmot-toolteadev: A Threat to npm Packages

inherent_marmot-toolteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104197: Malicious code in inherent_marmot-toolteadev (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 inherent_marmot-toolteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata and publish behavior.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the inherent_marmot-toolteadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary consequence of this vulnerability is the pollution of the npm registry with derivative packages, which can lead to confusion among developers and potential security risks if these packages are inadvertently used in projects.

How To Fix

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

npm uninstall inherent_marmot-toolteadev

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, avoid using the inherent_marmot-toolteadev package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The inherent_marmot-toolteadev package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for inherent_marmot-toolteadev →

Share this vulnerability

FAQ

inherent_marmot-toolteadev is an npm package that has been linked to malicious activities aimed at inflating developer reputation scores through the tea.xyz token reward campaign.

The vulnerability can lead to the pollution of the npm registry with malicious packages, which may confuse developers and introduce security risks if these packages are used.

You should uninstall the inherent_marmot-toolteadev package immediately and monitor your project for any potential impacts.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without requiring access to the code or installation.

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 inherent_marmot-toolteadev

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