Critical Malicious Code Vulnerability in hackerone-internal Package

hackerone-internal Updated 02 Oct 2025

Summary

24/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6223: Malicious code in hackerone-internal (npm). Affects hackerone-internal versions >= 10.0.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The hackerone-internal package is an npm module designed for internal use related to the HackerOne platform. It is intended to facilitate interactions with HackerOne's services. However, this package has been identified as malicious due to its ability to communicate with domains associated with harmful activities and execute commands that may compromise system security.

Vulnerability Detail

The vulnerability in the hackerone-internal package (version 10.0.1) arises from its malicious behavior, which includes communicating with a domain linked to malicious activities and executing potentially harmful commands. This can lead to unauthorized access, data breaches, and other security risks for users who have this package integrated into their applications.

How To Fix

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

npm uninstall hackerone-internal

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

If you cannot update the package immediately, consider removing the hackerone-internal package from your project until a secure version is available. You can do this by running: npm uninstall hackerone-internal.

Conclusion

The hackerone-internal package has been identified as having a critical vulnerability due to its malicious behavior. Users are strongly advised to update or remove the package to protect their applications from potential security threats. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in open-source dependencies.

See every vulnerability recorded for hackerone-internal →

Share this vulnerability

FAQ

The hackerone-internal package is an npm module used for internal operations related to the HackerOne platform.

It is considered malicious because it communicates with domains associated with harmful activities and executes commands that can compromise system security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the hackerone-internal package, it is advisable to uninstall it from your project until a secure version is released.

You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.

How To Fix

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

npm uninstall hackerone-internal

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