What does the aoflcorp malware do?

The OpenSSF Package Analysis project identified 'aoflcorp' @ 0.0.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of aoflcorp are malicious?

The following npm versions of aoflcorp are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate aoflcorp if I installed it?

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

If aoflcorp 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.

How do I find aoflcorp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aoflcorp (version 0.0.1).

Malicious package

aoflcorpnpm

Advisory published May 12, 2026Updated May 12, 2026

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

Malicious code in aoflcorp (npm)

MAL-2026-3613

Immediate action

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

npm uninstall aoflcorp

What this malware does

The OpenSSF Package Analysis project identified 'aoflcorp' @ 0.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bfc014b9e60bb1abb58d948abcf31112dd4c160ab8416317476f3c67c2e84d49

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

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