Malicious Code Detected in call-all Package: A Critical Security Alert

call-all Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16452: Malicious code in call-all (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 call-all package is an npm library designed to facilitate the invocation of multiple functions in a streamlined manner. It is commonly used in JavaScript applications to enhance code efficiency by allowing developers to call several functions with a single command. However, this package has recently been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the call-all package stems from the presence of malicious code that can compromise the integrity of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was confirmed by security researchers from Amazon Inspector, who reported it as a significant threat to users of the package.

How To Fix

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

npm uninstall call-all

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

If an immediate update is not feasible, consider removing the call-all package from your project temporarily and replacing its functionality with alternative methods to invoke multiple functions. This can be done by manually calling each function in sequence until a secure version of the package is available.

Conclusion

The discovery of malicious code within the call-all npm package poses a significant security threat to applications that utilize it. Users are strongly advised to update the package to the latest version or implement workarounds to mitigate potential risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for call-all →

Share this vulnerability

FAQ

The call-all package is an npm library that allows developers to invoke multiple functions with a single command, improving code efficiency.

The vulnerability involves malicious code embedded within the package, which can lead to security breaches and unauthorized access.

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

Consider removing the call-all package and replacing its functionality with alternative methods to invoke functions until a secure version is available.

The vulnerability was reported by security researchers from Amazon Inspector, highlighting the critical nature of the issue.

How To Fix

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

npm uninstall call-all

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