monogrok@1.0.7

monogrok 1.0.7 is a turnkey bulk phishing/spam toolkit. The package documents and implements: bulk SMTP credential rotation, SOCKS proxy rotation (functions/ipr/*), recipient-MX direct delivery that bypasses outbound mail relays (functions/snd/mailers/mxdml.js, mxsml.js), Microsoft EWS adapter (functions/snd/mailers/ewsml.js), Zimbra SOAP fallback, 75 link-obfuscation presets, 50 body/attachment encryption presets, attachment extension spoofing (e.g., deliver Attachment-1.html displayed as Invoice.pdf — documented in _init/.monotomic.help.txt as 'spoofs_attachment_extension_name'), AES-encrypted ZIP attachment building (functions/zip-archive.js), an email verifier/debouncer/sorter (functions/vrf/*, functions/deb/*), a redirect scanner (functions/rdt/*), and a credential 'judger' that probes IMAP/SMTP/EWS/Zimbra autodiscover (functions/jdg/*). Every reachable JS file in the tarball (~90 files across commands/, functions/, utils/, plus ultra.js, denv.js, helpers.js) is shipped as javascript-obfuscator output (rotating string array, hex-named identifiers, RC4/base64 decoder, self-defending wrappers); package.json confirms intent with a devDependency on javascript-obfuscator and an `obfuscate` script. The combination of MX-direct bypass + attachment-MIME spoofing + AES-encrypted attachments + SMTP/proxy rotation has no legitimate use case and is purpose-built for bulk phishing delivery while evading content scanners and sender reputation. ultra.js additionally calls `parseAsync(process.argv)` at the top level, so `require('monogrok')` immediately runs the CLI against the consumer's argv and mutates ~50 process.env keys via denv.js, plus triggers a license/sign-in flow that POSTs to the vendor backend at https://mntmc.rip. Installing or running this package puts the installer's domain, sending IPs, and organizational reputation at direct risk of blocklisting, abuse complaints, and legal exposure for participating in phishing campaigns. ## Source: ghsa-malware (d5c1f66e8c5e2e97b3fc1b3d8819b405e9187fc5fdd2cedc0882e018e2da56bd) 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.