Which versions of align-configer are malicious?

The following npm versions of align-configer are flagged malicious: 3.4.2, 3.4.3. Treat any of these as compromised.

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

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

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

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

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

Malicious package

align-configernpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

align-configer is a confirmed malicious npm package (MAL-2026-1653) that executes malicious code on install (malicious versions 3.4.2, 3.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in align-configer (npm)

MAL-2026-1653

Immediate action

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

npm uninstall align-configer

What this malware does

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

Malicious versions

2 flagged

3.4.23.4.3

Indicators of compromise (SHA-256)

49f43f76e93e2a6646a8f272d094aac9fc40bb970f4ff6c2079a42c600de414f

8a76e6de932ec68131ed43e8241b4a224deb6a87a78c4d6e2bc641680dc52e70

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01102

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks align-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