Which versions of ecto-spirit-core are malicious?

The following npm versions of ecto-spirit-core are flagged malicious: 1.0.0, 2.14.800, 3.45.100, 3.99.1. Treat any of these as compromised.

How do I remediate ecto-spirit-core if I installed it?

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

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

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

Search your lockfiles and build artifacts for ecto-spirit-core (4 malicious versions).

Malicious package

ecto-spirit-corenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

ecto-spirit-core is a confirmed malicious npm package (MAL-2026-2356) that executes malicious code on install (malicious versions 1.0.0, 2.14.800, 3.45.100…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ecto-spirit-core (npm)

MAL-2026-2356

Immediate action

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

npm uninstall ecto-spirit-core

What this malware does

The package ecto-spirit-core was found to contain malicious code.

Malicious versions

4 flagged

1.0.02.14.8003.45.1003.99.1

Indicators of compromise (SHA-256)

f86d5d2cfaa7768649f604dec60ddd07777bc549bf63e320f333ac0daac74610

72d3638a38fd250b18d9b93068dc16f07d03d34e87c361a41069ac57740f2629

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01749

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ecto-spirit-core-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