Critical Remote Code Execution Vulnerability in internallib_v463 Package

internallib_v463 Updated 24 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16481: Malicious code in internallib_v463 (npm). Affects internallib_v463 versions 1.0.2. 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 internallib_v463 package is an npm module designed for internal use, potentially providing various utility functions. However, it has been compromised to include malicious code that allows an attacker to gain unauthorized access to the host system. This vulnerability is particularly concerning due to its ability to establish a reverse shell, granting full control to the attacker.

Vulnerability Detail

The vulnerability originates from a malicious modification in the internallib_v463 package, specifically in the index.js file. The exported function 'command' executes a command that fetches a reverse shell script from a hardcoded IP address (10.0.73.186:443) and pipes it to the shell. This allows an attacker to gain interactive shell access to the victim's machine. The presence of a console log statement indicating hostile intent further confirms the malicious nature of this code. This vulnerability poses severe risks, including unauthorized access, data theft, and potential system compromise.

How To Fix

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

npm uninstall internallib_v463

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 remove the internallib_v463 package from your project until a secure version is released. You can do this by executing the following command: npm uninstall internallib_v463. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities.

Conclusion

The internallib_v463 package contains a critical vulnerability that allows for remote code execution through a reverse shell. It is essential to update or remove this package to protect your systems from potential attacks. Regular monitoring and auditing of dependencies can help prevent similar issues in the future.

See every vulnerability recorded for internallib_v463 →

Share this vulnerability

FAQ

The vulnerability allows for remote code execution through a reverse shell, enabling attackers to gain control over the host system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If an immediate update is not possible, consider removing the package temporarily and monitoring your application for any suspicious activity.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure that you only use trusted packages.

The consequences include unauthorized access to sensitive data, potential data loss, and complete system compromise.

How To Fix

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

npm uninstall internallib_v463

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