registry / @apexfdn/apex / 1.0.16

@apexfdn/apex@1.0.16

AI Security Review

scanned 3h ago · by lpm-firewall-ai

`postinstall` fetches an executable payload that is absent from the tarball and stores it under the package `bin` directory. Windows additionally receives a remote native addon under the package-branded `~/.apex` path. No integrity verification constrains either payload.

Static reason

One or more suspicious static signals were detected.

Trigger

npm installation, then user invocation of `apex`.

Impact

A release-asset or redirect compromise can supply arbitrary native code executed as the installing user.

Mechanism

Install-time remote binary and native-addon download followed by CLI execution.

Rationale

The package creates a real install-time remote code delivery surface because its executable payload is absent from the package and unverified. Source inspection does not establish an independently malicious objective, so this warrants a warning rather than a block.

Evidence

package.jsoninstall.cjsapex.cjsbin/apexREADME.md~/.apex/natives/16.3.6/pi_natives.win32-x64-baseline.node

Network endpoints1

github.com/Apex-Foundation/copilot/releases/download/v1.0.0/

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-10979

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in @apexfdn/apex (npm)

Details

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.

References

OSV advisory OpenSSF JSON ADVISORY

Decision evidence

public snapshot

AI called this Suspicious at 94.0% confidence as Dangerous Capability with low false-positive risk.

Evidence for block

`package.json` runs `node install.cjs` as `postinstall`.
`install.cjs` downloads a platform executable from `github.com/Apex-Foundation/copilot` during install.
Downloaded executable has no checksum, signature, or pinned integrity verification.
On Windows it also downloads a native `.node` addon to `~/.apex/natives/16.3.6`.
`apex.cjs` later executes the downloaded `bin/apex` with inherited environment variables.
`bin/apex` is empty in the inspected package; install supplies its executable payload remotely.

Evidence against

Installer skips execution when `CI` or `SKIP_APEX_INSTALL` is set.
The only observed network host is GitHub and the source contains no credential harvesting or exfiltration logic.
No shell command construction, `eval`, destructive deletion, or foreign AI-agent configuration mutation was found.
The wrapper's execution is user-invoked through the declared `apex` CLI bin.

Behavioral surface

Source

ChildProcessEnvironmentVarsFilesystemNetwork

Source & flagged code

2 flagged

package.jsonView file

•scripts.postinstall = node install.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node install.cjs

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

Source & flagged code

2 flagged · loading source

package.jsonView file

•scripts.postinstall = node install.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node install.cjs

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

Findings

1 High3 Medium3 Low

HighInstall Time Lifecycle Scriptspackage.json

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumNetwork

MediumEnvironment Vars

LowScripts Present

LowFilesystem

LowUrl Strings