Which versions of @aoflcorp/freighter are malicious?

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

How do I remediate @aoflcorp/freighter if I installed it?

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

If @aoflcorp/freighter 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 @aoflcorp/freighter part of a known attack campaign?

Yes — @aoflcorp/freighter is associated with the RLMA-2026-04663, RLUA-2026-05807 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 @aoflcorp/freighter across my projects, lockfiles, and CI pipelines?

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

Malicious package

@aoflcorp/freighternpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@aoflcorp/freighter is a confirmed malicious npm package (MAL-2026-7035) 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/freighter (npm)

MAL-2026-7035

Immediate action

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

npm uninstall @aoflcorp/freighter

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7921c79fc02d93920675f9586d5317657a563414c3cf343cfb3818bd7f575406

d7743eb52dcbc81c37a017488e08ea79fae90b5b3c15ab7426461901811b54c2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @aoflcorp/freighter (version 0.0.1).
If you installed it — respond
Remove @aoflcorp/freighter 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/freighter 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/freighter 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.

Campaign

RLMA-2026-04663RLUA-2026-05807

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @aoflcorp/freighter-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