Which versions of ecto-registry are malicious?

The following npm versions of ecto-registry are flagged malicious: 1.0.0, 2.14.800, 3.45.101. Treat any of these as compromised.

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

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

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

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

Search your lockfiles and build artifacts for ecto-registry (3 malicious versions).

Malicious package

ecto-registrynpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in ecto-registry (npm)

MAL-2026-2354

Immediate action

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

npm uninstall ecto-registry

What this malware does

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

Malicious versions

3 flagged

1.0.02.14.8003.45.101

Indicators of compromise (SHA-256)

8be350826b658e6ad71d85478fc4ed3c6a33e210f7980f39e9f9c477f89e62ee

b394438461d34fc5c46660addaa8e99dad23d16b7050b1e8635fd7c700ae723f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01747

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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