aes-decode-runner-pronpm

aes-decode-runner-pro ships an opaque 326-byte AES-GCM ciphertext (DEFAULT_FINAL_ENCODED_TEXT in src/config/defaults.js) along with a hardcoded passphrase (default-dev-passphrase) and salt (encode-npm-c-salt). The exported run() function (and runDefaultDecodedFunction() in src/pipeline/custom-codec-pipeline.js) decrypts this blob and executes the resulting string via new Function("require", runnable)(require), passing in the host's require so the decrypted code can load arbitrary Node modules (filesystem, network, child_process). The plaintext is not present in the source tree, so the actual code being run cannot be audited from the package contents. The README presents the package as an AES helper utility, but the package's primary documented entry point (pkg.run()) auto-executes hidden author-controlled code. There are no install lifecycle hooks, so npm install alone is benign; harm fires when a consumer calls the advertised run() API or runs npm start/npm test against the package. The combination of hardcoded ciphertext + hardcoded key + new Function execution sink + misleading cover-story README is the standard hidden-payload-runner shape and not a legitimate use of AES.

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.