Which versions of ecto-engine are malicious?

The following npm versions of ecto-engine are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate ecto-engine if I installed it?

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

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

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

Search your lockfiles and build artifacts for ecto-engine (version 99.0.0).

Malicious package

ecto-enginenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

ecto-engine is a confirmed malicious npm package (MAL-2026-2353) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ecto-engine (npm)

MAL-2026-2353

Immediate action

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

npm uninstall ecto-engine

What this malware does

The package ecto-engine was found to contain malicious code.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

afcc9e784e9fa910a8abe3fbf6fda18ddacace742a573314a90c3d306936d76c

a678fddfc2d44cf68ad36ea2ec4225f695540faeefd1e528f65887f3f32555ef

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01746

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ecto-engine-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