The npm Facebook Chat API package @eryxenx/fca sends caller credentials and a 2FA secret to minhdong.site instead of Facebook.
Anyone who logs a bot into Facebook through @eryxenx/fca 1.3.0 to 1.3.2 hands the password and a 2FA secret to an outside server. GitHub and Amazon Inspector published the finding on 20 November 2026.
What happened
GitHub published malware advisory GHSA-qhrc-mfjw-xwq3 on 20 November 2026. OpenSSF copied it as MAL-2026-20276, and Amazon Inspector found the behavior.
- The advisory covers
1.3.0,1.3.1and1.3.2, with no fixed version. - In
module/loginHelper.js,loginViaAPIPOSTs the caller-supplied Facebook email, password and Base32 2FA secret tohttps://minhdong.site/api/v1/facebook/login_ios. - The code then reads
uid,access_tokenand session cookies from the minhdong.site reply and installs them in the caller's cookie jar for.facebook.com. - I read
module/loginHelper.jsin 1.3.2 and 1.3.5. Both contain the same minhdong.site endpoint and POST. The advisory lists only 1.3.0 to 1.3.2, so versions 1.3.3 to 1.3.5 are unlisted. - The endpoint sends credentials only when the app calls
loginViaAPI, or whenfca-config.jsonsetsautoLoginto true. The code says auto-login through the external API is off by default.
Affected versions
- GitHub advisory and MAL-2026-20276:
= 1.3.0,= 1.3.1,= 1.3.2. - npm still serves the package, and its latest tag points to
1.3.5. - The advisory does not give publish dates for the three listed versions.
Indicators of compromise
https://minhdong.site/api/v1/facebook/login_iosfca-1.3.2.tgz(MAL-2026-20276) with SRIsha512-A+uYqOk/IsiNkhQumR3AKMnB/8MKeh+SQuNq0Ji+4crjJxsVqe28fp2RiHhCITQotubjG+kMaZ1ddwSdb15Y3Q==module/loginHelper.js(MAL-2026-20276) with SHA-256e056bd7e9aece1ef2131883cd1c2d2c56560d666c8bcf958d3eae9d2abfc7718src/remote/remoteClient.js(MAL-2026-20276) with SHA-256b3b67a5eead971c4575b2d910858955937cec7bc638c49383dda93726e9f6ccf
How to check
List the installed version in each Node.js project.
npm ls @eryxenx/fca
Search package-lock.json files in past builds for @eryxenx/fca. Those builds can show when an install pulled 1.3.0 to 1.3.2.
What to do now
- Run
npm uninstall @eryxenx/fcain every project that uses it. - If a bot logged in with your Facebook password through the package, treat that account as exposed. From a clean device, change the Facebook password and end all other sessions.
- The package takes the Base32 2FA secret, not a one-time code. Reset two-factor authentication for the account from a clean device.
- If the login ran inside a build or a server, rotate the secrets stored on that machine.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `@eryxenx/fca` 1.3.2. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
@eryxenx/fca 1.3.2
A Facebook chat library sends the account password and a 2FA secret to an outside server instead of Facebook.
No security team? See who reads the alert.
Frequently asked questions
Does @eryxenx/fca send my Facebook password to Facebook directly?
The loginViaAPI flow sends it to minhdong.site first. That server returns the session cookies the package then installs for Facebook.
Which versions does GitHub mark as malware?
Versions 1.3.0, 1.3.1 and 1.3.2. The latest tag on npm points to 1.3.5, and my inspection found the same login flow in 1.3.5.
Who found this attack?
Amazon Inspector reported it. OpenSSF published MAL-2026-20276 on 20 November 2026 and GitHub reviewed it the same day.
Sources
Send this page to the person who looks after AI at your company.