Which versions of ectoplast-spirit are malicious?

The following npm versions of ectoplast-spirit are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ectoplast-spirit if I installed it?

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

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

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

Search your lockfiles and build artifacts for ectoplast-spirit (version 1.0.0).

Malicious package

ectoplast-spiritnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

ectoplast-spirit is a confirmed malicious npm package (MAL-2026-2357) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ectoplast-spirit (npm)

MAL-2026-2357

Immediate action

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

npm uninstall ectoplast-spirit

What this malware does

The package ectoplast-spirit was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bd27edd2b5041ed8d4e1e8adf054346fdfb58cf4d59d5a67c15eae0e7bb2aa75

efb7edb34ad0e4e3740692b2f80f2ec2085ad2557e947920c3acdd71626a8b99

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01750

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ectoplast-spirit-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