Malicious Code Injection in magnificent_dinosaur_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95350: Malicious code in magnificent_dinosaur_requirement (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 magnificent_dinosaur_requirement package is part of the npm ecosystem, which is widely used for managing JavaScript packages. 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 exploits npm's package management system, leading to significant security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the magnificent_dinosaur_requirement package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to manipulate the npm registry. Specifically, the malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only inflates developer reputation scores fraudulently but also pollutes the npm registry with potentially harmful packages, posing risks to users who may inadvertently install them.

How To Fix

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

npm uninstall magnificent_dinosaur_requirement

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 magnificent_dinosaur_requirement package from your project until a secure version is released. This can be done using the command: 'npm uninstall magnificent_dinosaur_requirement'. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The magnificent_dinosaur_requirement package poses a significant security risk due to its association with malicious activities aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for magnificent_dinosaur_requirement →

Share this vulnerability

FAQ

It is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the installation of malicious code that compromises your application's integrity and security.

You should update the package to the latest version or uninstall it until a secure version is available.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code or install anything.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall magnificent_dinosaur_requirement

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