Critical Malicious Code Vulnerability in internallib_v30 Package

internallib_v30 Updated 06 Oct 2026

Summary

06/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17633: Malicious code in internallib_v30 (npm). Affects internallib_v30 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 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_v30 package, available via npm, is designed for internal use but lacks clear documentation and legitimate functionality. Its primary file, index.js, contains malicious code that compromises the security of any system that installs it. The package is suspected to be a target for dependency confusion attacks, given its ambiguous name and empty metadata.

Vulnerability Detail

The vulnerability originates from the internallib_v30 package version 1.0.1, which includes a command in its index.js file that executes a remote shell script from a malicious server. When the exported command() function is invoked, it runs '/bin/bash -c' with a curl command that fetches and executes a script from 'https://reverse-shell.sh/10.0.19.80:8443'. This action opens a reverse shell, allowing attackers to gain unauthorized access to the host system. The lack of legitimate purpose and the presence of embedded malicious code classify this as a severe security threat.

How To Fix

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

npm uninstall internallib_v30

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

There are no direct workarounds for this vulnerability due to the nature of the malicious code. The best approach is to ensure that the internallib_v30 package is not included in your project dependencies.

Conclusion

The internallib_v30 package poses a significant security risk due to its embedded malicious code that can lead to unauthorized access. It is crucial to remove this package from any projects and to monitor for vulnerabilities using tools like Vulert.

See every vulnerability recorded for internallib_v30 →

Share this vulnerability

FAQ

internallib_v30 is an npm package that appears to serve internal purposes but contains malicious code that can compromise system security.

The vulnerability allows an attacker to execute a remote shell script on the host system, opening a reverse shell that grants unauthorized access.

You should uninstall the internallib_v30 package immediately using 'npm uninstall internallib_v30' to protect your system.

Currently, there is no patched version of the internallib_v30 package available, so it is advised to avoid using it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall internallib_v30

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