MAL-2026-18195 Malicious code in darknode-cli (npm)

Package is a command-line offensive-security / pentest toolkit. The flagged files (lib/nexus/pentest-engine.js, lib/toolkit/network.js, lib/toolkit/web-scanner.js, lib/toolkit/wireless-iot.js, lib/toolkit/cloud-security.js, lib/toolkit/exploit-db.js, lib/toolkit/cve-lookup.js, lib/nexus/attack-planner.js, lib/nexus/methodologies.js, lib/nexus/security-kb.js, lib/nexus/git-security.js) catalog offensive tool names (nmap, nikto, gobuster, sqlmap, hydra, john, hashcat, etc.), sensitive-file extension lists (.pem,.key,.env,.credentials), dynamic-DNS indicators (no-ip, duckdns) in an incident-response knowledge base, and shell/HTTP primitives used to drive those tools against operator-chosen external targets. lib/nexus/api-server.js and lib/cli/api-server.js expose local HTTP control surfaces that the CLI itself consumes. package.json declares no preinstall/install/postinstall lifecycle hooks, so installing the package does not auto-execute these capabilities. No code path reads installer secrets (~/.aws, ~/.ssh, ~/.npmrc, browser or wallet stores), scrapes process.env wholesale, or exfiltrates installer-side data to a hardcoded author-controlled destination; the base64/Buffer usage in lib/toolkit/encoders.js and lib/toolkit/jwt.js is standard encoder/JWT handling. The offensive capability is directed at targets the operator explicitly provides at runtime, consistent with a legitimate penetration-testing utility.

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.