fca-nx@6.6.9
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo install-time hook, self-dependency, hidden downloader, or package-controlled non-Facebook receiver was found. The environment-controlled DGW path nonetheless forwards session cookies to arbitrary URLs when enabled, leaving a concrete unresolved credential-exfiltration risk.
Decision evidence
public snapshot- The optional DGW path sends the logged-in session cookie header to endpoints supplied through environment variables.
- The package automatically invokes its E2EE connection during login; the DGW feature can run after E2EE connects when its environment switch is set.
- package.json has no preinstall, install, postinstall, or prepare hook.
- E2EE activation is normally gated by an explicit config flag or option.
- The ordinary E2EE endpoints are Facebook and Messenger hosts, matching this Messenger API package.
- Remote-control networking is disabled in the default project configuration.
Source & flagged code
15 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.9.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.6.9 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.