fca-nx@6.7.2
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe explicit gate prevents treating this as covert automatic exfiltration, but it does not restrict credentials to Facebook-controlled destinations. The unrestricted credential-forwarding capability warrants a warning.
Decision evidence
public snapshot- The package declares a CommonJS entrypoint and only test and lint scripts, with no install lifecycle hook.
- An E2EE path is gated by an explicit environment flag but accepts three operator-supplied WebSocket endpoint URLs and builds a cookie header from the active app state.
- The WebSocket connection sends that constructed cookie header as the Cookie request header to each supplied URL.
- Thread information requests use the Facebook GraphQL endpoint with the session jar.
- User information requests use Facebook GraphQL with the session jar.
- The credential-forwarding path requires FB_DGW_ENABLE=1 and at least one endpoint environment variable.
- No fixed non-Facebook recipient or automatic install-time execution was found.
Source & flagged code
7 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.2.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.7.2 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.