Malicious Code Detected in internal-random Package - Vulnerability MAL-2025-6732

internal-random Updated 02 Oct 2025

Summary

01/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6732: Malicious code in internal-random (npm). Affects internal-random versions >= 16.0.0. 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 internal-random package is an npm library designed to provide random number generation functionalities. It is commonly used in applications that require secure and unpredictable random values. However, this package has been found to communicate with a domain associated with malicious activities, raising significant security concerns for users relying on its functionality.

Vulnerability Detail

The vulnerability identified as MAL-2025-6732 originates from version 16.0.0 of the internal-random package. It involves the package's communication with a malicious domain, which could potentially lead to data breaches, unauthorized access, or other malicious activities. Users of this package are at risk of exposing sensitive information or compromising their applications due to this malicious behavior.

How To Fix

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

npm uninstall internal-random

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 may consider removing the internal-random package from your project until a secure version is released. You can do this by executing: 'npm uninstall internal-random'. Alternatively, you can replace it with a different library that provides similar functionalities without the associated risks.

Conclusion

The internal-random package has been identified as having a serious vulnerability that allows communication with a malicious domain. Users are advised to update or remove the package to protect their applications from potential threats. Regular monitoring of dependencies is crucial for maintaining application security.

See every vulnerability recorded for internal-random →

Share this vulnerability

FAQ

The internal-random package is an npm library used for generating random numbers, often utilized in applications requiring secure random values.

This vulnerability involves the internal-random package communicating with a domain linked to malicious activities, posing security risks to users.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Update the internal-random package to the latest version using 'npm update internal-random' or consider removing it until a secure version is available.

Failure to address this vulnerability could lead to data breaches, unauthorized access to sensitive information, and overall compromise of your application.

How To Fix

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

npm uninstall internal-random

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