fca-nx@6.7.0
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe scanner's exfiltration signal maps to Facebook API and explicitly configured networking, not a package-controlled default receiver. The only cookie-forwarding DGW path requires an explicit environment flag and endpoint configuration.
Decision evidence
public snapshot- The manifest defines only test and lint scripts, with no install lifecycle hook.
- The flagged upload function processes its caller-supplied link input and uses a Facebook upload endpoint.
- The E2EE DGW path is inactive unless an explicit environment flag is set, then uses operator-supplied endpoint variables.
- The flagged dynamic require enumerates JavaScript files only in the package's local database directory.
- No hardcoded non-Facebook credential receiver or automatic exfiltration path was found.
- Remote control is disabled by default with no default URL.
- Credential API login refuses to run without a caller or configuration-supplied server.
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.0.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.7.0 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.