wallet-analytics (npm) · Malicious Code

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bfc85c0238f90672b0cc329cae3487061924ed5a6458644a97cd90a830ace807) index.js exports a getPlugin function that issues an HTTPS request to a hardcoded bare-IP endpoint at https://46.183.25.232:45000/icons/<n> and passes the response's `credits` field to `new Function('require','module',...,data.credits)`, invoking the returned function with a live `require`, `process`, and `Buffer` in scope. Any consumer that loads the package's default export executes attacker-supplied JavaScript with full Node privileges on the host. The C2 URL is assembled from split literals (protocol/separator/domain/path) alongside a decoy setDefaultModule that constructs cdnjs font-awesome URLs, disguising the traffic as icon-CDN requests, and the authorization header is spelled `bearrtoken` to further avoid casual inspection. Declared dependencies (@primno/dpapi for Windows DPAPI unwrap, better-sqlite3, node-machine-id) are consistent with follow-on wallet and browser-secret harvesting delivered by the remote payload. ## Source: ghsa-malware (d5d588d45a7677764b972a1892308e61160b2803021af65ba25b1d47534fa264) 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.

• npmjs.com/package/wallet-analytics/v/1.4.8 (opens in a new tab)
• github.com/advisories/GHSA-xf3p-c585-94jr (opens in a new tab)