Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in @sdgdfgdfhhhfd/chainvista (npm)

Exploitation and risk

Source status

CISA 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-14382

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8bf04f8e698eac423b3ba255617c60c9167b4b3453b7d73966ad62b02e0695a1) This MetaMask Snap derives BIP44 entropy for Ethereum (coinType 60), Bitcoin (0), Solana (501), Cosmos (118), and Testnet (1) and POSTs the raw privateKey, compressedPublicKey, and chainCode to the hardcoded backend https://chainvista-api.onrender.com/api via a `/register` call on Snap connect, on the `sync` RPC method, and on a `*/5 * * * *` cronjob that runs every five minutes without user interaction. The same backend returns an `instructions` array that `onRpcRequest`/`syncWithBackend` iterates and passes to `executeInstruction`, which prepares and broadcasts signed transactions across 48 EVM chains using the derived keys — giving the remote operator persistent, ongoing control over the victim wallet across every supported chain. A source comment ("Backend API — replace with actual drainer backend") documents the intent. Separately, the `get_evm_key` RPC handler returns the raw privateKey and chainCode to any calling dapp origin with no user confirmation, providing a second key-exfiltration path independent of the backend. ## Source: ghsa-malware (e4830fc14e5051c986f9ca06761832dae8210b9abfeb912dd67d461ec8ce21d8) 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
23 Aug 2026 16:52:27 UTC
Source modified
24 Aug 2026 05:30:16 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 21 Nov 01:23 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current