preferenceslifecycle-paypalnpm
Advisory published Updated
preferenceslifecycle-paypal is a confirmed malicious npm package (MAL-2026-11062) that opens a backdoor for remote access (malicious versions 24.0.0, 28.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in preferenceslifecycle-paypal (npm)
What this malware does
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.
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for preferenceslifecycle-paypal (2 malicious versions).
If you installed it — respond
preferenceslifecycle-paypal establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If preferenceslifecycle-paypal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks preferenceslifecycle-paypal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.