Critical Malicious Code Vulnerability in open2internet Package

open2internet Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190853: Malicious code in open2internet (npm). Affects open2internet versions 0.1.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 open2internet package is an npm library designed to facilitate internet connectivity and data transfer functionalities in JavaScript applications. It is often utilized in web development projects for its ease of use and integration capabilities. However, this package has been identified as containing malicious code, which poses significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the open2internet package, which has been flagged for containing embedded malicious code. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete system takeover by an external entity. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall open2internet

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 workaround, if you need similar functionality, consider using alternative packages that provide internet connectivity features without the associated risks. Always verify the integrity and reputation of any package before installation.

Conclusion

The open2internet package has been identified as a significant security risk due to embedded malicious code. Users must take immediate action to uninstall the package and secure their systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for open2internet →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall open2internet' and rotate any sensitive information stored on the affected system.

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

No, there is currently no patched version available for the open2internet package. The only solution is to remove it completely.

Failing to address this vulnerability can lead to unauthorized access to your system, data theft, and potential control by malicious actors.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, providing an easy way to keep your applications secure.

How To Fix

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

npm uninstall open2internet

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