supply chain event / NVI-00010942 / Revision 1
Malicious code in fca-raihan (npm)
GitHub lists this malware advisory for fca-raihan, fca-raihan. 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.
fca-raihan
source listed= 37.2.5
## Source: amazon-inspector (241006adda5ea773d76d48d874c80a4054215ed18f05de3e392cdd86c0379785) package.json for fca-raihan declares a dependency whose key equals the package's own name (`fca-raihan`) with source `github:raihan9099/fca-raihan`. This is an off-registry dependency source with no ref pin and no integrity check: on `npm install`, npm fetches the current HEAD of that GitHub repository and installs whatever tree it returns, running any lifecycle scripts contained in the fetched code. Whoever controls the repository can change what gets installed at any time, independently of what is published to the npm registry, and the self-named dependency-confusion shape (dependency key equal to the package's own name) causes this source to be resolved during normal installs of fca-raihan. Additional patterns observed in the shipped source include Buffer.from(..., 'base64') decoding in messaging/e2ee modules and `ping` string occurrences in a bundled Facebook e2ee vendor file; these are consistent with the package's advertised messaging/E2EE functionality and are not by themselves indicative of installer harm, but they are not analyzable independently of whatever the mutable GitHub so
fca-raihan
source listed= 37.2.6
## Source: amazon-inspector (241006adda5ea773d76d48d874c80a4054215ed18f05de3e392cdd86c0379785) package.json for fca-raihan declares a dependency whose key equals the package's own name (`fca-raihan`) with source `github:raihan9099/fca-raihan`. This is an off-registry dependency source with no ref pin and no integrity check: on `npm install`, npm fetches the current HEAD of that GitHub repository and installs whatever tree it returns, running any lifecycle scripts contained in the fetched code. Whoever controls the repository can change what gets installed at any time, independently of what is published to the npm registry, and the self-named dependency-confusion shape (dependency key equal to the package's own name) causes this source to be resolved during normal installs of fca-raihan. Additional patterns observed in the shipped source include Buffer.from(..., 'base64') decoding in messaging/e2ee modules and `ping` string occurrences in a bundled Facebook e2ee vendor file; these are consistent with the package's advertised messaging/E2EE functionality and are not by themselves indicative of installer harm, but they are not analyzable independently of whatever the mutable GitHub so
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-gmjq-r5g4-xc73 ↗
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.