🛡️ MAL-2026-10979 — apex

Malicious code in @apexfdn/apex (npm)

Source: amazon-inspector

On npm install, install.js runs as a postinstall step and downloads a platform-specific executable from https://github.com/Apex-Foundation/copilot/releases/download/v<VERSION>/<assetName>, writes it to BIN_PATH, and chmods it 0755 on non-Windows. No hash or signature verification is performed. The package.json declares repository can1357/oh-my-pi and homepage omp.sh, and the shipped README describes an unrelated project (@oh-my-pi/pi-coding-agent, the omp coding agent by can1357) — neither matches the Apex-Foundation/copilot GitHub org the binary is pulled from. The declared main and exports point to a TypeScript tree that is not present in the tarball; the only shipped runtime artifacts are apex.js, install.js, and a bin shim. apex.js unconditionally spawns the downloaded binary with the user's environment on every CLI invocation. The publisher/source mismatch, cover-story README impersonating an unrelated coding-agent project, and unverified execution of third-party bytes at install time constitute a mismatched-publisher dropper: npm install @apexfdn/apex causes attacker-controlled bytes from a third-party GitHub org to be fetched and staged as an executable that then runs against the installer's environment.

Source: ghsa-malware

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.