fca-nx@6.7.3
Facebook Messenger API for Node.js — Fast, Secure, and Feature-Rich
AI Security Review
scanned 25d ago · by lpm-firewall-aiStatic review shows a Facebook Messenger client with no install lifecycle, no obfuscated loader, and requests aimed at Facebook or an opt-in caller endpoint. Optional update checks and remote control do not form a concrete attack chain.
Decision evidence
public snapshot- package.json exposes index.js and only test and lint scripts, with no preinstall, install, or postinstall hook and no self-dependency.
- The bundled E2EE client connects to Facebook Messenger websocket and registration hosts for session encryption.
- getThreadInfo posts thread queries to the Facebook GraphQL batch endpoint.
- getUserInfo posts profile lookups to Facebook chat and GraphQL endpoints using the caller session jar.
- Remote control is created only when the caller sets config.remoteControl.enabled, and it does not run at install time.
- Login later queries registry.npmjs.org for a newer fca-nx version and only prints an update warning.
- The optional remote websocket is user-configured and sends user id, region, and package version as a hello, not a hidden default recipient.
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.3.
See all versions of fca-nx for other recorded verdicts.
- Review the evidence and your use of fca-nx@6.7.3 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.