Malicious Code Detected in external-api Package - MAL-2025-20105

external-api Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20105: Malicious code in external-api (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 external-api package is an npm library designed to facilitate interactions with various external APIs. It provides developers with a streamlined way to integrate third-party services into their applications. However, this package has been found to contain malicious code, posing significant security risks to users who implement it in their projects.

Vulnerability Detail

The vulnerability in the external-api package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was identified in version 0 and has been documented as MAL-2025-20105, highlighting the urgency for users to address this vulnerability.

How To Fix

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

npm uninstall external-api

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 measure, users can avoid using the external-api package until a secure version is released. Alternatively, consider using a different library that provides similar functionality without the associated risks.

Conclusion

The external-api package has been identified as containing malicious code, which poses a serious risk to applications that utilize it. Users are urged to update the package as soon as a patched version is available or to seek alternative solutions in the meantime. Utilizing tools like Vulert can help monitor for vulnerabilities in your projects.

See every vulnerability recorded for external-api →

Share this vulnerability

FAQ

The external-api package is an npm library that helps developers interact with various external APIs, simplifying the integration of third-party services.

The malicious code can lead to unauthorized access and data breaches, potentially compromising the security of applications that utilize this package.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

As of now, there is no patched version available. Users should monitor the package repository for updates and apply them as soon as they are released.

If you cannot update the package right away, consider using alternative libraries that offer similar functionality without the security risks associated with external-api.

How To Fix

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

npm uninstall external-api

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