Which versions of superacli are malicious?

The following npm versions of superacli are flagged malicious: 1.14.0, 1.15.0. Treat any of these as compromised.

How do I remediate superacli if I installed it?

superacli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed superacli — how do I know if it already compromised me?

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

Yes — superacli is associated with the IN-MAL-2026-003210, IN-MAL-2026-003209 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 superacli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for superacli (2 malicious versions).

Malicious package

superaclinpm

Advisory published May 19, 2026Updated May 26, 2026

superacli is a confirmed malicious npm package (MAL-2026-4674) that opens a backdoor for remote access (malicious versions 1.14.0, 1.15.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in superacli (npm)

MAL-2026-4674

Immediate action

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

npm uninstall superacli

What this malware does

plugins/gopass/daemon.js opens an outbound WebSocket connection to a hardcoded bare IP ws://92.113.145.178:8768 (defaulted via process.env.GOPASS_UI_URL || 'ws://92.113.145.178:8768') using a hardcoded shared secret gopass-daemon-shared-secret-2024 as its auth token. After connecting, the daemon registers the local hostname and platform with the remote peer, then accepts inbound 'command' messages and executes them against the user's local gopass password store (show/insert/delete/sync/generate via spawn('bash',...)), returning command stdout — including decrypted secrets — to the remote operator. plugins/gopass/.daemon-config ships the same bare-IP URL as a default. Any user who runs the documented gopass daemon command on this package hands remote control of their password manager to whoever controls 92.113.145.178, with no per-installer authentication challenge. The destination is not a publisher-owned domain; it is a bare IP. This is a backdoor / silent-relay against the installer's most sensitive local secret store.

Malicious versions

2 flagged

1.14.01.15.0

Indicators of compromise (SHA-256)

6c45fea405a610447f72926e8663afc4151606f39189d380bf929ad09419908b

d7d9550b726186fac26a503604bdd620b6b242326db4f06d04e79b37c7a88438

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for superacli (2 malicious versions).
If you installed it — respond
superacli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If superacli 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. superacli on npm has been identified as a malicious package (versions 1.14.0, 1.15.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003210IN-MAL-2026-003209

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks superacli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database