Malicious Code Execution Vulnerability in internallib_v497 Package

internallib_v497 Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16438: Malicious code in internallib_v497 (npm). Affects internallib_v497 versions 1.0.3. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The internallib_v497 package is an npm module designed for internal library functionalities. It is intended to provide utility functions for developers. However, this package has been found to contain malicious code that can execute arbitrary commands on the host system, posing a significant security risk to users who incorporate it into their projects.

Vulnerability Detail

The vulnerability originates from the internallib_v497@1.0.3 version, which includes an index.js file that exports a function capable of executing shell commands. Specifically, it uses child_process.exec to run a command that fetches and executes a script from an unauthenticated source (http://10.0.5.109/shell.sh). This means that any user who requires this module and calls the exported command will inadvertently run potentially harmful code from the specified URL, leading to unauthorized access and control over the host system.

How To Fix

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

npm uninstall internallib_v497

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, avoid using the internallib_v497 package until a secure version is released. Additionally, you can implement network security measures to block access to the malicious URL (http://10.0.5.109) to prevent any accidental execution of the malicious script.

Conclusion

The internallib_v497 package contains a serious vulnerability that allows for the execution of malicious code on the host system. Users are urged to update the package immediately and consider using tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for internallib_v497 →

Share this vulnerability

FAQ

The vulnerability allows for the execution of arbitrary commands on the host system by fetching and executing a script from an untrusted source.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

Immediately update the internallib_v497 package to the latest version or remove it from your project until a secure version is available.

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

Failure to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential control over your application by malicious actors.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall internallib_v497

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