fca-nx@6.7.1
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a dangerous opt-in capability rather than confirmed malware: it forwards an existing service session to unrestricted operator-configured endpoints. The explicit gate prevents treating it as covert default theft, but it does not bind the destination to Facebook.
Decision evidence
public snapshot- An opt-in environment flag enables a DGW connection using operator-supplied endpoint URLs.
- The connection builds a Cookie header from the active Facebook application state and supplies it to every configured WebSocket URL.
- The DGW connection is invoked after E2EE startup, so the forwarding path is reachable when enabled.
- The manifest has no preinstall, install, or postinstall lifecycle hook.
- The conventional thread and user lookup code sends requests only to Facebook endpoints.
Source & flagged code
8 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
src/api/socket/e2ee/vendor/fb-e2ee.cjsView on unpkg · L130Package contains a high-severity secret pattern.
src/api/socket/e2ee/vendor/fb-e2ee.cjsView on unpkg · L2964Findings
Affected versions and remediation
This report applies to fca-nx@6.7.1.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.7.1 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.