@apexfnd/apex (npm) · Malicious Code
Affects @apexfnd/apexSource GCVE Database
Malicious package : remove @apexfnd/apex and rotate any secrets on hosts that installed it.
Data as of 5 Aug 2026, 17:07 UTC
Malicious package
Published to npm · OSV MAL-2026-11121
What to do
Remove @apexfnd/apex from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@apexfnd/apex | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package @apexfnd/apex versions 1.0.0, 1.0.1, 1.0.3, and 1.0.4 contains malicious postinstall scripts that execute attacker-controlled code during installation. On macOS, it runs an AppleScript that downloads and executes a shell script with root privileges after prompting the user for their password. On all platforms, it downloads a platform-specific binary from an attacker-controlled GitHub repository and installs it without verifying its integrity. The package metadata does not match the domains from which code and binaries are fetched, indicating a supply chain compromise.