Which versions of ssh-common are malicious?

The following npm versions of ssh-common are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate ssh-common if I installed it?

Remove ssh-common 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 ssh-common — how do I know if it already compromised me?

If ssh-common 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 ssh-common part of a known attack campaign?

Yes — ssh-common is associated with the RLMA-2026-01818 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 ssh-common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ssh-common (2 malicious versions).

Malicious package

ssh-commonnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

ssh-common is a confirmed malicious npm package (MAL-2026-2390) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ssh-common (npm)

MAL-2026-2390

Immediate action

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

npm uninstall ssh-common

What this malware does

The package ssh-common was found to contain malicious code.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

dc71528ace5be29fc5ebb4a10fd2d742666b607eb6655f03c47ce40ffc2d624e

d42bf2b2b77d94173694ed6e952fc5efb2d0de3b04f237f15ffa9470809a321e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ssh-common (2 malicious versions).
If you installed it — respond
Remove ssh-common 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 ssh-common 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. ssh-common on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01818

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ssh-common-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