Malicious Code Injection in mipta190-noise-former: A Threat to npm Ecosystem

mipta190-noise-former Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160461: Malicious code in mipta190-noise-former (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 mipta190-noise-former package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.

Vulnerability Detail

The mipta190-noise-former package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme associated with the tea.xyz token reward campaign, which floods the npm registry with numerous derivative packages to manipulate developer reputation. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security risks in their applications.

How To Fix

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

npm uninstall mipta190-noise-former

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 measure, you can avoid using the mipta190-noise-former package altogether. If it is already installed, you can uninstall it using the command: npm uninstall mipta190-noise-former.

Conclusion

The mipta190-noise-former package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry. Developers are urged to remove this package and monitor their applications for vulnerabilities to maintain security.

See every vulnerability recorded for mipta190-noise-former →

Share this vulnerability

FAQ

mipta190-noise-former is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability in your application.

You should uninstall the mipta190-noise-former package immediately to mitigate any potential risks.

Currently, there is no patched version available. It is advisable to remove the package until a secure version is released.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall mipta190-noise-former

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