Which versions of paypal-postman-lib are malicious?

The following npm versions of paypal-postman-lib are flagged malicious: 1.0.1, 2.0.9. Treat any of these as compromised.

How do I remediate paypal-postman-lib if I installed it?

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.

I already installed paypal-postman-lib — how do I know if it already compromised me?

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.

Is paypal-postman-lib part of a known attack campaign?

Yes — paypal-postman-lib is associated with the RLMA-2025-05480, IN-MAL-2026-007400 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find paypal-postman-lib across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paypal-postman-lib (2 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.

Malicious package

paypal-postman-libnpm

Malicious code in paypal-postman-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-47594

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall paypal-postman-lib

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.

Malicious versions

2 flagged

1.0.12.0.9

Indicators of compromise (SHA-256)

13bca4cc804039a9cee17a27be7ba13744b8bb36f93904268c21e4291a5e8835

c2b733a611e3d27e56f4c6ee549bbcf3d88a1c823512c13797440c4c13f2712c

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paypal-postman-lib (2 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

No. paypal-postman-lib on npm has been identified as a malicious package (versions 1.0.1, 2.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05480IN-MAL-2026-007400

References

npmjs.com

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.

Malware detection Runtime egress monitoring