Malicious code in xo-twofa (npm)
MAL-2026-11105 · GHSA-7v73-c7c7-mr5x
Published · Modified
Dependency scanning
Check whether xo-twofa is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (47761909a1686ad1db2239f5055c8526e38ac88c07060c886157d157d15b4315)
package.json declares a preinstall script that runs node index.js on npm install. index.js collects host identifiers (os.hostname(), os.platform(), os.arch(), os.homedir(), dns.getServers()) and POSTs them as JSON to the hardcoded host f4k2mnpoengdb7o3etftn7fmkdq5ew5ku.oastify.com (a Burp Collaborator out-of-band interaction endpoint). The beacon fires automatically on install without user interaction and self-describes as a dependency-confusion proof of concept.
Source: ghsa-malware (3b53f3137f847d7234a065286565e0112a828bb14dd580d6ea46a9c262397294)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes