@apexfdn/apex
This report shows the evidence for @apexfdn/apex@1.0.29. 32 of 33 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10979 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The package is an unverified remote-binary carrier activated during installation, which is a real unresolved supply-chain risk. Source inspection does not establish malicious behavior of the absent payload.
Independent scan evidence
public snapshot- package.json runs `node install.cjs` in postinstall.
- install.cjs downloads platform executables from github.com/Apex-Foundation/copilot.
- install.cjs follows redirects and performs no checksum or signature validation.
- install.cjs downloads a Windows native addon to ~/.apex/natives.
- apex.cjs executes the downloaded bin/apex with inherited environment.
- Installer source contains no credential harvesting or exfiltration.
- No agent-config mutation or destructive filesystem action is present.
- Downloaded binary is not bundled, so its behavior cannot be established by source inspection.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
install.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @apexfdn/apex@1.0.29.
The versions list below shows the verdict for each recorded version.
- Avoid installing @apexfdn/apex@1.0.29. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.