Which versions of es1int-configer are malicious?

The following npm versions of es1int-configer are flagged malicious: 3.3.0, 3.3.1. Treat any of these as compromised.

How do I remediate es1int-configer if I installed it?

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

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

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

Search your lockfiles and build artifacts for es1int-configer (2 malicious versions).

Malicious package

es1int-configernpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

es1int-configer is a confirmed malicious npm package (MAL-2026-1727) that executes malicious code on install (malicious versions 3.3.0, 3.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in es1int-configer (npm)

MAL-2026-1727

Immediate action

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

npm uninstall es1int-configer

What this malware does

The package es1int-configer was found to contain malicious code.

Malicious versions

2 flagged

3.3.03.3.1

Indicators of compromise (SHA-256)

dcba4a8bd15a8dcea892a7a46123dae4d41e4ea7e27c9efe35680efb17baa834

c5e6a102d4a76da1cac7b4f5ad35f5178e00170cbe76b1ddbc2f56fedde201de

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01291

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks es1int-configer-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