fca-nx@1.8.5
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe static hints correspond to a Messenger API with bundled E2EE code, not a concrete malicious chain. No install-time execution or unconsented exfiltration/control-surface mutation was found.
Decision evidence
public snapshot- After successful login, runtime auto-connects an E2EE client using the logged-in session.
- The E2EE feature writes its device store under the calling project's .fca-nx directory.
- package.json has no preinstall, install, postinstall, or other lifecycle hook.
- All observed fixed service endpoints are Facebook/Meta Messenger endpoints aligned with the package purpose.
- Remote WebSocket support is disabled by default and requires an operator-supplied URL.
- Dynamic loading only targets a package-relative missing lib/index.mjs fallback; no payload is present.
- No credential harvesting, third-party exfiltration, shell execution, or AI-agent configuration writes were found.
Source & flagged code
12 flagged · loading sourcePackage contains a high-severity secret pattern.
e2ee/vendor/fb-e2ee.cjsView on unpkg · L2964Package source references weak cryptographic algorithms.
e2ee/vendor/fb-e2ee.cjsView on unpkg · L130Findings
Affected versions and remediation
This report applies to fca-nx@1.8.5.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@1.8.5 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.