Security readout for executives and security teams
Plain-English summary
CVE-2019-19771 describes a malicious npm package named lodahs, likely intended to catch users who mistyped lodash. The source states version 0.0.1 is a Trojan horse that finds and exfiltrates cryptocurrency wallets. Business risk is concentrated where developers, build systems, or applications installed lodahs instead of lodash.
Executive priority
Handle as a targeted supply-chain cleanup and credential-theft incident if found. The urgent question is whether lodahs was ever installed in environments containing cryptocurrency wallets or sensitive developer material.
Technical view
The issue is not a coding flaw in lodash; it is a malicious Node.js package publication. The CVE description identifies lodahs 0.0.1 as a Trojan horse targeting cryptocurrency wallet data. The bundle does not provide CVSS, CWE, patch details, or affected CPEs beyond the lodahs package.
Likely exposure
Exposure is likely limited to environments where npm package lodahs version 0.0.1 was installed, directly or through lockfiles. Highest concern is developer workstations, CI runners, or application hosts with cryptocurrency wallet material present.
Exploitation context
The source describes the package itself as malicious and wallet-exfiltrating. It may have been installed by typosquatting against lodash. The bundle does not show KEV listing or other evidence of ongoing active exploitation campaigns.
Researcher notes
Evidence is sparse but direct: the CVE states lodahs 0.0.1 is a Trojan horse that exfiltrates cryptocurrency wallets. No CVSS, CWE, exploit telemetry, or vendor fix details are provided in the bundle.
Mitigation direction
- Remove lodahs from package manifests, lockfiles, and deployed environments.
- Install the intended lodash package only if actually required.
- Treat cryptocurrency wallets on exposed systems as potentially compromised.
- Review npm advisory and package guidance before assuming remediation is complete.
- Add dependency review controls for typosquatted package names.
Validation and detection
- Search package.json and lockfiles for lodahs and version 0.0.1.
- Review SBOMs and dependency inventories for lodahs entries.
- Check developer workstations, CI runners, and build images for prior installation.
- Confirm lodash dependencies are spelled correctly and sourced from expected packages.
- Review wallet exposure on any system where lodahs was installed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-19771 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.npmjs.com/package/lodahsCVE reference · x_refsource_MISC
- https://www.npmjs.com/advisories/1417CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.