Malicious Code Detected in exiouss Package: Potential Data Exfiltration Risk

exiouss Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17327: Malicious code in exiouss (npm). Affects exiouss versions 5.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The exiouss package, available on npm, is designed for various functionalities within Node.js applications. However, version 5.0.1 has been identified with a critical vulnerability that allows for malicious code execution. This vulnerability poses a significant risk as it can lead to unauthorized data access and exfiltration.

Vulnerability Detail

The vulnerability originates from the main.js file in exiouss@5.0.1, which imports the child_process module and makes POST requests to hardcoded endpoints, including public and internal addresses. The presence of an internal address alongside a public one indicates potential malicious intent, as it suggests active data exfiltration or reconnaissance activities. The repeated use of ping commands throughout the code further supports this theory, marking the package as a potential threat to users' data security.

How To Fix

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

npm uninstall exiouss

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 exiouss package from your project until a secure version is released. You can do this by executing the command: npm uninstall exiouss.

Conclusion

The exiouss package version 5.0.1 contains a serious vulnerability that could lead to malicious code execution and data exfiltration. Users are advised to update the package or remove it until a secure version is available. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for exiouss →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can lead to unauthorized data access and potential data exfiltration.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

Yes, using Vulert, you can monitor your dependencies for vulnerabilities by analyzing your package-lock.json file.

Failing to address this vulnerability can lead to data breaches, unauthorized access to sensitive information, and potential exploitation of your application.

How To Fix

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

npm uninstall exiouss

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