fca-eryxenx
Facebook Chat API by EryXenX | Stable • Auto Re-login • Full E2EE Support — send messages, media, reactions & more in encrypted chats, hassle-free
This report shows the evidence for fca-eryxenx@39.2.8. 5 of 7 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource confirms a default third-party credential receiver and reachable runtime paths that transmit supplied Facebook secrets. Absence of lifecycle hooks does not mitigate this credential-exfiltration behavior.
Decision evidence
public snapshot- Default configuration enables automatic login through minhdong.site.
- loginViaAPI posts supplied email and password to the configured external server.
- Normal credential login invokes the external token-login path when no appState/cookie is supplied.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The external-login behavior is documented, but it forwards Facebook credentials to a non-Facebook default host.
Source & flagged code
11 flagged · loading sourcePackage contains a high-severity secret pattern.
src/api/socket/e2ee/vendor/fme/dist/index.cjsView on unpkg · L303Google API key in src/api/socket/e2ee/vendor/fme/dist/index.cjs
src/api/socket/e2ee/vendor/fme/dist/index.cjsView on unpkg · L303Findings
Affected versions and remediation
This report applies to fca-eryxenx@39.2.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing fca-eryxenx@39.2.8. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.