Malicious Code Injection in moaning_mink_0xrequest: A Threat to npm Packages

moaning_mink_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105912: Malicious code in moaning_mink_0xrequest (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 'moaning_mink_0xrequest' is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to alter critical files and continuously republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'moaning_mink_0xrequest' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, which can lead to significant security risks including the proliferation of malicious packages in the npm ecosystem. The continuous republishing of these variants can undermine the integrity of the npm registry and potentially expose users to further vulnerabilities.

How To Fix

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

npm uninstall moaning_mink_0xrequest

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 affected package from your project by executing 'npm uninstall moaning_mink_0xrequest'. This will prevent any malicious code from executing while you seek a secure alternative or wait for a patched version.

Conclusion

The 'moaning_mink_0xrequest' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Users are encouraged to take immediate action to remove the package and monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for moaning_mink_0xrequest →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to modify package.json and republish variants, which can lead to security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Using this package can lead to the proliferation of malicious variants in the npm registry, potentially compromising your application's security and integrity.

Regularly updating your dependencies and using tools like Vulert to monitor for vulnerabilities can help prevent similar issues.

It is advisable to uninstall the package immediately and review your project for any potential impacts or further vulnerabilities.

How To Fix

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

npm uninstall moaning_mink_0xrequest

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