shadowx-fca@10.5.0
Facebook Chat API - Modified by Mueid Mursalin Rifat
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner signals map to normal Messenger/E2EE functionality, fixed local loading, and opt-in features. Source inspection found no lifecycle execution, command execution, stealth persistence, or concrete data exfiltration.
Decision evidence
public snapshot- No npm lifecycle hook is declared.
- External credential submission requires a configured apiServer.
- Remote WebSocket control is disabled by default.
- Runtime network calls target Facebook and npm registry endpoints.
- No child-process, shell, payload-download, or broad file-harvesting code found.
- The dynamic import targets a fixed package-local lib path.
- E2EE state persistence is package-specific session storage after user login.
Source & flagged code
12 flagged · loading sourcePackage contains a high-severity secret pattern.
e2ee/vendor/fb-e2ee.cjsView on unpkg · L2964Package source references weak cryptographic algorithms.
e2ee/vendor/fb-e2ee.cjsView on unpkg · L130Findings
Affected versions and remediation
This report applies to shadowx-fca@10.5.0.
See all versions of shadowx-fca for other recorded verdicts.
- Review the evidence and your use of shadowx-fca@10.5.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.