Malicious Code Injection in hot_marlin_0xrequest Package - npm Vulnerability

hot_marlin_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103811: Malicious code in hot_marlin_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The hot_marlin_0xrequest 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 known to flood npm with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the hot_marlin_0xrequest package arises from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms. The ramifications include potential pollution of the npm registry, compromised developer reputations, and the risk of inadvertently using compromised packages in projects.

How To Fix

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

npm uninstall hot_marlin_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, avoid using the hot_marlin_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any updates or vulnerabilities.

Conclusion

The hot_marlin_0xrequest package poses a significant risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for hot_marlin_0xrequest →

Share this vulnerability

FAQ

The hot_marlin_0xrequest package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.

This vulnerability can lead to the pollution of the npm registry and may compromise your project's integrity by introducing malicious code or dependencies.

If you have installed the hot_marlin_0xrequest package, you should uninstall it immediately using 'npm uninstall hot_marlin_0xrequest' and check your package-lock.json for any references.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application's vulnerability status using the Vulert playground.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and consider employing tools like Vulert for real-time monitoring.

How To Fix

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

npm uninstall hot_marlin_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