Malicious code in exnesss (npm)

---

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (184796b4aafee8400786643e9f43338886de2166171c62879cfd4c023655b487)

Package name 'exnesss' typosquats 'exness'. The package.json declares scripts.postinstall: 'node./postinstall.js', and postinstall.js issues an HTTPS GET to a hardcoded Burp Collaborator subdomain (hteimcuxkeb6pacscuexz4d9y04rshg6.oastify.com) on every install. This fires automatically on npm install, contacting an out-of-band interaction host that reveals the installer's network/DNS metadata to the operator of that Collaborator instance. The package provides no advertised functionality to the installer beyond the beacon.

Source: ghsa-malware (ad099cf1562a64265f95bdeb06afd1aa99185aa58559cb04e7b94efbf6ac6cc6)

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: ossf-package-analysis (9547bba265ba397413387555d1bf269b1072ec4aba26409f22c72654c110cbf1)

The OpenSSF Package Analysis project identified 'exnesss' @ 0.0.1 (npm) as malicious.

It is considered malicious because:

• The package communicates with a domain associated with malicious activity.