fca-nx@6.6.6
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings map to a Messenger client and bundled E2EE implementation, with Facebook-only protocol endpoints in the inspected paths. Sensitive external destinations are unset or disabled by default and require operator configuration.
Decision evidence
public snapshot- The bundled E2EE client sends registration data to a Facebook host.
- The E2EE bridge files load a bundled protocol client.
- Thread and user API methods send requests to Facebook endpoints.
- Remote control and external credential-login targets require enabled operator configuration.
- The manifest has no install lifecycle hook.
- No package-controlled receiver, credential harvesting, shell execution, or install-time execution was found.
- The reported network and file operations implement the Messenger API and E2EE session storage.
- The default configuration disables remote control and has no external API server.
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.6.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.6.6 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.