Malicious Code Vulnerability in signer-app: npm Package Compromised

signer-app Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1847: Malicious code in signer-app (npm). Affects signer-app versions 100.0.0. 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 signer-app is an npm package designed for managing digital signatures and enhancing security in applications that require authentication. It is widely used due to its ease of integration and robust features. However, recent findings have revealed that this package has been compromised, exposing users to potential security threats.

Vulnerability Detail

The vulnerability identified in the signer-app package is characterized by the presence of malicious code that can execute unauthorized actions within the user's environment. This issue originated from a specific version of the package (100.0.0) and was reported by ReversingLabs. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data breaches, and exploitation of the affected systems. Users of this package are at risk if they do not take immediate action to mitigate the threat.

How To Fix

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

npm uninstall signer-app

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 compromised version (100.0.0) of the signer-app package. Instead, consider using an alternative package that offers similar functionality without the associated risks.

Conclusion

The malicious code vulnerability in the signer-app npm package poses significant risks to users. It is crucial to take immediate action by updating to a secure version or implementing workarounds to mitigate potential threats. Staying informed and proactive is essential in maintaining application security.

See every vulnerability recorded for signer-app →

Share this vulnerability

FAQ

The signer-app package is an npm library used for managing digital signatures and enhancing security in applications.

The vulnerability was discovered by ReversingLabs, which identified malicious code within the signer-app package.

The risks include unauthorized access to sensitive data, potential data breaches, and exploitation of affected systems.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If immediate updates are not possible, consider using an alternative package or implementing additional security measures to protect your application.

How To Fix

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

npm uninstall signer-app

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