Which versions of signer-app are malicious?

The following npm versions of signer-app are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate signer-app if I installed it?

Remove signer-app from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed signer-app — how do I know if it already compromised me?

If signer-app was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is signer-app part of a known attack campaign?

Yes — signer-app is associated with the RLMA-2026-01573 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find signer-app across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for signer-app (version 100.0.0).

Malicious package

signer-appnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

signer-app is a confirmed malicious npm package (MAL-2026-1847) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in signer-app (npm)

MAL-2026-1847

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall signer-app

What this malware does

The package signer-app was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

0a8c6333b6196af2ed389df90274197e09837168bed89906f23a26842df65e8a

4b301c6e6ca05f396b336ffb3bf41042d7ea226645dc1f455ca12e7f6ff04f01

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for signer-app (version 100.0.0).
If you installed it — respond
Remove signer-app from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If signer-app was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. signer-app on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01573

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks signer-app-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database