expect-dotenvnpm

The package's main entry runs a worker that performs an HTTPS GET to https://realase-0626.vercel.app/api/v1 and passes the response's parser string into vm.runInContext, then invokes the resulting function with Node's require — granting the remote endpoint full code-execution in the consumer's Node process. The destination URL is concealed as a hex byte array in constants.js (pluginIDs) and reassembled at runtime via String.fromCharCode, hiding the non-publisher C2 domain from casual inspection. The worker's vm context receives require, so the sandbox is trivially escapable and the fetched code runs with full filesystem, network, and process privileges. This behavior fires on require('expect-dotenv') followed by .config() or .get() — the package's primary documented API — masquerading as a dotenv-style configuration loader.

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.