Malicious Code Injection in past_halibut_0xrequest Package

past_halibut_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106945: Malicious code in past_halibut_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 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 past_halibut_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing scripts. However, it has been identified as malicious due to its functionality that modifies package metadata and generates numerous derivative packages to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the software supply chain. The malicious nature of this package poses significant risks to developers and users, as it can lead to unintentional usage of compromised packages.

How To Fix

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

npm uninstall past_halibut_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 avoid using the past_halibut_0xrequest package and replace it with a trusted alternative that provides similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The past_halibut_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain software integrity.

See every vulnerability recorded for past_halibut_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the introduction of malicious code, compromising the integrity of your project and potentially affecting users.

You should uninstall the package immediately and check your package-lock.json for any references to it.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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