Critical Malicious Code Vulnerability in internallib_v875 Package

internallib_v875 Updated 06 Oct 2026

Summary

06/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17635: Malicious code in internallib_v875 (npm). Affects internallib_v875 versions 1.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 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 internallib_v875 package is an npm library designed for internal use, but it has been found to contain malicious code. This package is intended to provide certain functionalities, but its integrity has been compromised, making it a potential threat to any application that includes it.

Vulnerability Detail

The vulnerability originates from the internallib_v875 package, which contains an index.js file that exports a command() function. This function executes a shell command using /bin/bash -c, which fetches a reverse-shell payload from a hardcoded endpoint (10.0.19.80:8443) via curl piped to sh. This allows an attacker to gain an interactive shell on the host running the package, posing a severe security risk. The malicious code is executed without any verification, and the package lacks legitimate functionality, making it a clear case of embedded malicious code.

How To Fix

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

npm uninstall internallib_v875

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 command() function from the internallib_v875 package. Instead, consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The internallib_v875 package contains a critical vulnerability that allows for the execution of malicious code, posing a significant risk to any application that utilizes it. Immediate action is required to remove the package and safeguard your system.

See every vulnerability recorded for internallib_v875 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that executes a reverse shell command, allowing attackers to gain unauthorized access to the host.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your package-lock.json file for any affected packages.

Immediately remove the package from your project and check for any signs of compromise in your application.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall internallib_v875

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