Malicious code in ddok-modal (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-10497
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0326cd953f229feb020dd3c1cd882246b6bac2cb0be8ffe9e47d063d9f59c9c6) ddok-modal presents itself as a reusable React wallet-connection modal supporting MetaMask, Phantom, Rabby, TronLink, Bitget, Coinbase, and Solflare, but the modal UIs are credential-harvesting impersonations of those wallets. Each wallet 'unlock' modal binds an onChange handler that calls sendKeyToBackend(userId, 'cha', newKeyword, <wallet_type>) on every keystroke and a submit handler that calls sendKeyToBackend(..., 'enter', keyword,...) on form submission, POSTing the captured password / recovery phrase to https://api.wagmiwallet.org/api/keys (with a websocket fallback at wss://api.wagmiwallet.org) and a secondary endpoint at https://wagmirequest.la. The payload includes user_id, key_type, the captured keys, wallet_type, and the visitor's IP address and geolocation (collected via api.ipify.org and ipapi.co at modal open). The modals reproduce real wallet copy ('Enter your password', 'Secret Recovery Phrase', 'MetaMask can't recover your password') and reference legitimate browser-extension IDs (e.g. nkbihfbeogaeaoehlefnkodbefgpgknn for MetaMask) to look authentic. Any web application that embeds this component relays its end users' wallet passwords and seed phrases to the package author's hardcoded infrastructure. ## Source: ghsa-malware (71fe082b3de64bf70b24ca38d1b8f64dbac1f9c9fe55a0403137c9f53a3fcbf4) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 13 Jul 2026 21:44:42 UTC
- Source modified
- 30 Sep 2026 16:45:04 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.