MalwarePublished 4 Aug 2026Updated 4 Nov 2026

exnesss (npm) · Malicious Code

Affects exnesssSource GCVE Database

Malicious package : remove exnesss and rotate any secrets on hosts that installed it.

Data as of 5 Nov 2026, 00:42 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-11518

What to do

Remove exnesss from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmexnesss	Affected =0.0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The 'exnesss' npm package (version 0.0.1) is a malicious typosquatting package targeting the legitimate 'exness' package. Upon installation, it executes a postinstall script that makes an HTTPS request to a hardcoded Burp Collaborator domain, leaking network and DNS metadata of the installer to an attacker-controlled server. The package provides no legitimate functionality and is considered fully compromising to any system where it is installed.

Impact

Installation of the 'exnesss' package results in network metadata leakage to an attacker-controlled server, potentially exposing sensitive network information. The package is considered fully compromising, implying that attackers may have gained control over the affected system. All secrets and keys on the compromised system should be rotated immediately from a secure environment. Removal of the package alone may not fully remediate the compromise.

Defensive guidance

Remove the 'exnesss' package immediately if installed. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Because the package may have allowed full system compromise, further forensic analysis and remediation may be necessary.

Summary

The 'exnesss' package on npm is a typosquatting malware that impersonates the legitimate 'exness' package. Its package.json includes a postinstall script that automatically runs on 'npm install' and sends an HTTPS GET request to a Burp Collaborator subdomain (hteimcuxkeb6pacscuexz4d9y04rshg6.oastify.com), leaking network and DNS metadata of the host machine to the attacker. The package offers no functional utility beyond this beaconing behavior. Security sources classify any system with this package installed as fully compromised, recommending immediate secret and key rotation from a different machine and removal of the package, though removal may not eliminate all malicious artifacts.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 00:42 UTC

Technical details

References

Community reviews