Malicious Code Injection in corporate_minnow-notthedev Package

corporate_minnow-notthedev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101011: Malicious code in corporate_minnow-notthedev (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The corporate_minnow-notthedev package is part of the npm ecosystem and is typically used for various development purposes. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. This package is associated with the tea.xyz token reward scheme, which has led to the proliferation of numerous derivative packages that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the corporate_minnow-notthedev 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 goal of this malicious activity is to inflate developer reputation scores for token rewards, leading to the continuous republishing of these compromised packages, which pollutes the npm registry and poses a significant risk to developers relying on these packages.

How To Fix

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

npm uninstall corporate_minnow-notthedev

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 corporate_minnow-notthedev package and replace it with a reputable alternative that serves the same purpose. Additionally, you can monitor your project for any instances of this package using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The corporate_minnow-notthedev package poses a significant risk due to its malicious code that alters project files and inflates developer reputation scores. It is essential to remove this package and monitor your projects for vulnerabilities to maintain the integrity of your development environment.

See every vulnerability recorded for corporate_minnow-notthedev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code modifies your package.json file and can lead to the continuous republishing of compromised packages, affecting your project's integrity.

You should remove the corporate_minnow-notthedev package from your project immediately and monitor for any updates or patches.

Yes, you can use the Vulert playground to check your application for vulnerabilities without needing to sign up.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file.

How To Fix

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

npm uninstall corporate_minnow-notthedev

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