fca-nx@6.6.7
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source establishes a real credential-forwarding capability to arbitrary configured endpoints, but it is explicitly gated and has no install-time execution. This warrants a warning rather than a block.
Decision evidence
public snapshot- The E2EE DGW mode accepts arbitrary nonempty WebSocket endpoints from environment variables and assembles the logged-in account's cookies into a header.
- The DGW socket sends that cookie header to every configured endpoint without a host allowlist.
- package.json has no install lifecycle hook.
- The risky DGW path requires both explicit E2EE activation and explicit environment settings; fixed service calls target Facebook domains.
Source & flagged code
14 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
e2ee/vendor/fb-e2ee.cjsView on unpkg · L130Package contains a high-severity secret pattern.
e2ee/vendor/fb-e2ee.cjsView on unpkg · L2964Findings
Affected versions and remediation
This report applies to fca-nx@6.6.7.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.6.7 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.