If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (e33d1db03ba9b9f1d9dc9f4c81a574e5baa69549e6c1897230540fe15d2749a3)
The package's preinstall hook executes index.js, which collects host identifiers (os.hostname(), os.platform(), os.arch(), os.homedir(), and dns.getServers()) and POSTs them as JSON to the hardcoded host ucahu2x3m2osjmwim8n8vmn1ssykmnac.oastify.com (a Burp Collaborator out-of-band domain) at /hit. The transmission is unconditional and fires automatically on npm install without any documented purpose or opt-in. The package name resembles internal-package/scope conventions, matching a dependency-confusion beaconing pattern where install-time execution confirms resolution of an attacker-published lookalike inside a target environment.
Source: ghsa-malware (8741695d3ce21420a88f903f03c16da4621561d07117127b656f91488c9b58f5)
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.
Source: ossf-package-analysis (14f6d8ebd40b7b46436b5f7fb622b770e061258ffa89d74fec858f27eb6a5327)
The OpenSSF Package Analysis project identified 'preferenceslifecycle-paypal' @ 28.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.