kijai

The package advertises itself as a high-throughput bulk-mail tool and ships every one of its ~50 JS files (cli.js, denv.js, helpers.js, all commands/*.js, all functions/**/*.js, queue/*, web/*, utils/*) as obfuscator.io-packed bundles with rotated string arrays, hex-named identifiers, and self-defending wrappers. README is a single sentence with no API docs. Functionality includes SOCKS proxy rotation (with four hardcoded proxies in _init/socks.txt), multi-threaded SMTP sending, fake-identity generation, masked-email helpers, an `encryptAndObfuscateAttachment3` helper that injects `eval(decode(...))` zero-width-character payloads into HTML attachments, EML smuggling, and Microsoft account-existence probing via GetCredentialType. The `verify` subcommand fetches https://login.live.com/login.srf and runs `eval()` on a regex-extracted `var ServerData = {...}` block from the response body, which is unsafe content evaluation but fires only when an operator explicitly runs `kijai verify`. package.json declares no preinstall/install/postinstall/prepare scripts; `main` and `bin` both point at a commander-based cli.js, so `npm install kijai` and a transitive `require()` do not auto-execute the abusive code paths. The advertised functionality targets third-party mail recipients and Microsoft account endpoints, not the developer who installs the package, so this does not satisfy the installer-harm gate (no exfiltration, no credential theft, no install-time destruction, no backdoor against the installer). Wholesale obfuscation of an abusive-purpose tool published openly on npm is policy-relevant and warrants human review for registry-abuse / ToS grounds, but it is not a supply-chain attack against installers under this system's scope. ## Source: ghsa-malware (f5db4f6fb4cd8bc8073e03771776ba865f51f852120bd44162573774905ccf22) 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.