Which versions of alfasec are malicious?

The following npm versions of alfasec are flagged malicious: 1.2.0, 1.2.1, 2.0.0, 3.0.0, 4.0.0, 5.0.0, 6.0.0, 7.0.0. Treat any of these as compromised.

How do I remediate alfasec if I installed it?

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

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

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

Search your lockfiles and build artifacts for alfasec (8 malicious versions).

Malicious package

alfasecnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

alfasec is a confirmed malicious npm package (MAL-2026-1652) that executes malicious code on install (malicious versions 1.2.0, 1.2.1, 2.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in alfasec (npm)

MAL-2026-1652

Immediate action

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

npm uninstall alfasec

What this malware does

The package alfasec was found to contain malicious code.

Malicious versions

8 flagged

1.2.01.2.12.0.03.0.04.0.05.0.06.0.07.0.0

Indicators of compromise (SHA-256)

f172f4fb2ceff06f0412a2f3ab7b16f11821de7bc3af4f5ce7bb65c15964483b

a35524fe277f853c2365b7fdeeb88c494ecd1f85436077d4692a92de3fdfe92a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for alfasec (8 malicious versions).
If you installed it — respond
Remove alfasec 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 alfasec 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. alfasec on npm has been identified as a malicious package (versions 1.2.0, 1.2.1, 2.0.0, 3.0.0, 4.0.0, 5.0.0, 6.0.0, 7.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01101

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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