Which versions of aonote are malicious?

The following npm versions of aonote are flagged malicious: 0.11.1. Treat any of these as compromised.

How do I remediate aonote if I installed it?

aonote is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed aonote — how do I know if it already compromised me?

If aonote was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is aonote part of a known attack campaign?

Yes — aonote is associated with the IN-MAL-2026-004808 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 aonote across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aonote (version 0.11.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aonote across your stack and pipelines.

Malicious package

aonotenpm

Malicious code in aonote (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4480

Immediate action

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

npm uninstall aonote

What this malware does

package.json declares "preinstall": "./scripts/postbuild", where scripts/postbuild is a 976KB UPX-packed Linux x86-64 ELF (sha256 36abd242...) shipped in the tarball with no source, no documentation, and no relation to the package's stated purpose (a JavaScript Arweave/AO note SDK). The binary executes unconditionally on every npm install on Linux. Strings inside the binary include kernel/loader paths (/lib64, nux-x86-), UPX self-tag (http://upx.sf.net), eBPF and ptrace symbols (LIBBPF_0.0, _PTRACE), cryptographic primitives (RSA_PKCS1_, Ed25519, MLKEM), HTTP client strings (HTTP/1.1), and host-identity references (USERPROFILE, BY_FAMILY). Package metadata is hollow (description: "", author: ""), consistent with a hijack of a previously-legitimate name or an attacker-published lure. A JS SDK has no legitimate need to execute an opaque packed native binary at install time; the UPX packing additionally hides the payload from static review. Any developer or CI pipeline running npm install aonote on Linux executes attacker-controlled native code with the invoking user's privileges.

This package was compromised as part of the IronWorm campaign. This campaign executes a malicious binary payload during installation via a preinstall hook. The payload is a Rust-built infostealer that targets developer environments, scanning for and harvesting credentials related to cloud providers, object storage, databases, source-control, package registries, and AI developer tools. It also targets cryptocurrency wallets, specifically injecting a malicious JavaScript hook into the Exodus desktop wallet to capture passwords and recovery phrases. Furthermore, the malware exhibits worm-like behavior by stealing GitHub and NPM credentials to push malicious updates to the victim's repositories and publish trojanized packages, and it uses an eBPF-based kernel rootkit to hide its processes and network connections on Linux systems.

Malicious versions

1 flagged

0.11.1

Indicators of compromise (SHA-256)

df30872a579b6ce2419993ff9bad621f42347097dd43551a26583223e6a98a7b

146faaf0d97c6a533a969bc3f3f117811f9317dc865ed4ab37f1679842ddeaae

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aonote (version 0.11.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aonote across your stack and pipelines.
If you installed it — respond
aonote is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If aonote was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks aonote before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. aonote on npm has been identified as a malicious package (version 0.11.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004808

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aonote-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring