paypal-postman-libnpm
paypal-postman-lib is a confirmed malicious npm package (MAL-2025-47594) that typosquats a legitimate package to trick installs (malicious versions 1.0.1, 1.0.2, 2.0.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in paypal-postman-lib (npm)
What this malware does
The package communicates with a domain associated with malicious activity.
The package's index.js imports os, fs, and https at the top level and reads os.hostname() and os.userInfo() before sending the collected host identity over an outbound HTTPS request. The package name impersonates PayPal/Postman branding while shipping no legitimate library functionality, and the only observable behavior is collection and transmission of installer host data. Installing or requiring this package causes the installer's hostname and OS user identity to be sent to a third-party endpoint.
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.
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 paypal-postman-lib (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paypal-postman-lib across your stack and pipelines.
If you installed it — respond
paypal-postman-lib is a typosquat — you almost certainly intended a legitimately-named package. Remove paypal-postman-lib, 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 paypal-postman-lib 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 paypal-postman-lib 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
- ReversingLabs · finder
Detect & block this
O3 blocks paypal-postman-lib-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.