Which versions of express-configers are malicious?

The following npm versions of express-configers are flagged malicious: 2.4.3. Treat any of these as compromised.

How do I remediate express-configers if I installed it?

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

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

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

Search your lockfiles and build artifacts for express-configers (version 2.4.3).

Malicious package

express-configersnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

express-configers is a confirmed malicious npm package (MAL-2026-1730) that executes malicious code on install (malicious version 2.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-configers (npm)

MAL-2026-1730

Immediate action

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

npm uninstall express-configers

What this malware does

The package express-configers was found to contain malicious code.

Malicious versions

1 flagged

2.4.3

Indicators of compromise (SHA-256)

2d87c5980a3b18b1c7283805a08a1caaa409394d527a272aa94dade2b371e456

5a9cfdc0f6b353580eb8a7c49a034123cbc9e7666eecf209fcc1eca4ca21c7dc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01304

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks express-configers-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