Malicious Code Detected in exapp Package - Security Alert

exapp Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20034: Malicious code in exapp (npm). Affected versions are not published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The exapp package is a Node.js application designed for various functionalities within the npm ecosystem. It is utilized by developers for its ease of integration and utility in building applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the exapp package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue is critical as it affects all versions starting from the initial release, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall exapp

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, users can remove the exapp package from their project until a secure version is released. This can be done by executing the command: npm uninstall exapp. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The exapp package has been identified to contain malicious code, posing serious security threats to applications that utilize it. Users are urged to take immediate action by updating or removing the package until a secure version is available. Regular monitoring of dependencies is crucial to maintain application security.

See every vulnerability recorded for exapp →

Share this vulnerability

FAQ

The exapp package is a Node.js application used for various functionalities in the npm ecosystem.

The malicious code can lead to unauthorized access and exploitation of systems using the exapp package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patch available. Users should monitor the package repository for updates.

As a temporary measure, consider uninstalling the exapp package and using alternative solutions until a secure version is released.

How To Fix

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

npm uninstall exapp

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