supply chain event / NVI-00009838 / Revision 1
Malicious code in hridoy-ultimate (npm)
GitHub lists this malware advisory for hridoy-ultimate. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
hridoy-ultimate
source listed= 8.0.0
## Source: amazon-inspector (221c8e51e1341e954c4f2ea3ea4a139606138c8ecc1ab99e17f403e304f05157) hridoy-ultimate 8.0.0 is an unofficial Facebook chat client that contains two installer-harming behaviors. First, the password-based login path in module/loginHelper.js forwards caller-supplied Facebook email, password, and Base32 TOTP 2FA secret to a hardcoded third-party endpoint at https://minhdong.site/api/v1/facebook/login_ios (default baked into module/config.js, not disclosed in README) and receives the resulting Facebook session cookies / access_token back through that server, giving the operator of minhdong.site full access to any account whose credentials pass through this path. Second, package.json declares `fca-unofficial` as `github:VangBanLaNhat/fca-unofficial` with no commit SHA or tag; npm resolves this against whatever the referenced repository's default branch contains at install time, and the vendor bundle under src/api/socket/e2ee/ actually requires that module, so arbitrary code controlled by that GitHub repo owner is pulled and executed on the installer at install and load time with no integrity check and no version lock. A separate opt-in WebSocket remote-control cl
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-8chm-j6jp-f4h3 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.