payoutsvettingserv-paypalnpm
payoutsvettingserv-paypal is a confirmed malicious npm package (MAL-2026-11058) that typosquats a legitimate package to trick installs (malicious versions 24.0.0, 28.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in payoutsvettingserv-paypal (npm)
What this malware does
[email protected] declares preinstall: node index.js in package.json, causing index.js to run automatically on npm install. The script collects host identifiers via os.hostname(), os.platform(), os.arch(), os.homedir(), and DNS server info, then POSTs them as JSON to a hardcoded Burp Collaborator subdomain at 2y1pgajb8aa05uiq8g9ghu99e0ks8twi.oastify.com/hit over HTTPS. The package name mimics an internal PayPal-style service, consistent with a dependency-confusion reconnaissance payload targeting build systems that mis-resolve an internal name to the public npm registry.
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 'payoutsvettingserv-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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for payoutsvettingserv-paypal (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging payoutsvettingserv-paypal across your stack and pipelines.
If you installed it — respond
payoutsvettingserv-paypal is a typosquat — you almost certainly intended a legitimately-named package. Remove payoutsvettingserv-paypal, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If payoutsvettingserv-paypal was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks payoutsvettingserv-paypal before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks payoutsvettingserv-paypal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.