Malicious Code Injection in capacitor-notificationhandler: A Critical Vulnerability

Summary

16/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-47394: Malicious code in capacitor-notificationhandler (npm). Affects capacitor-notificationhandler versions 0.0.2 – 0.0.3. 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 capacitor-notificationhandler package is an npm library designed to facilitate the handling of notifications in applications built with Capacitor. It provides developers with an easy way to manage notifications across different platforms. However, this package has been compromised, leading to the introduction of malicious code that poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from a compromise of the capacitor-notificationhandler package, specifically versions 0.0.2 and 0.0.3. The malicious code, introduced by the Shai-Hulud NPM worm, is designed to steal tokens and credentials from users' applications. This stolen data is then published to GitHub, and the worm propagates itself to other NPM packages owned by the affected user. The implications of this vulnerability are severe, as it can lead to unauthorized access to sensitive information and further compromise of the user's software ecosystem.

How To Fix

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

npm uninstall capacitor-notificationhandler

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 compromised package from your project until a secure version is available. You can do this by running the following command: npm uninstall capacitor-notificationhandler. Additionally, consider using alternative notification handling libraries that are not affected by this vulnerability.

Conclusion

The capacitor-notificationhandler package has been compromised, leading to a significant security vulnerability that can expose sensitive user data. It is crucial for developers to update to a secure version of the package and consider alternative solutions while monitoring their applications for any signs of compromise.

See every vulnerability recorded for capacitor-notificationhandler →

Share this vulnerability

FAQ

It is an npm library used for managing notifications in applications built with Capacitor.

The package was compromised by the Shai-Hulud NPM worm, which injected malicious code into specific versions.

The malicious code is designed to steal tokens and credentials from users' applications.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

As a temporary measure, consider uninstalling the compromised package and using alternative libraries until a secure version is available.

How To Fix

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

npm uninstall capacitor-notificationhandler

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