baileys-mbuilder@4.5.0-custom

package.json declares `"postinstall": "node lib/index.js --install"`, and lib/index.js is a single ~6.3 MB JSFuck-style eval() expression that reconstructs its source character-by-character from boolean/array coercions and %-unescape. The same file is the package's `main`, and lib/index.mjs re-requires it, so both `npm install` and any subsequent `require`/`import` of the package execute the obfuscated payload. The README documents that the postinstall step downloads MessageBuilder.js from a remote repository and that `MB.enableAutoUpdate(ms, cb)` periodically re-fetches remote JavaScript, hash-compares it, and on mismatch dynamic-`import()`s the new module, rebinding the default export via a Proxy so consumers transparently run the newly fetched code. The fetch destination, pinning, and any integrity checks are hidden inside the JSFuck blob and are not visible to static review. The obfuscation scale (6 MB of JSFuck for a message-builder library) has no legitimate purpose and defeats scanner and reviewer inspection of what actually executes on installer machines. ## Source: ghsa-malware (396af19b57be005328e2697ade736320c214b8f997f5deca03911df68b4c7e63) 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.