Which versions of paypal-business-sdk are malicious?

The following npm versions of paypal-business-sdk are flagged malicious: 9.4.3. Treat any of these as compromised.

How do I remediate paypal-business-sdk if I installed it?

paypal-business-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed paypal-business-sdk — how do I know if it already compromised me?

If paypal-business-sdk 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.

Is paypal-business-sdk part of a known attack campaign?

Yes — paypal-business-sdk is associated with the IN-MAL-2026-018635 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-business-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for paypal-business-sdk (version 9.4.3).

Malicious package

paypal-business-sdknpm

Advisory published Aug 24, 2026Updated Aug 24, 2026

paypal-business-sdk is a confirmed malicious npm package (MAL-2026-14435) that steals credentials and exfiltrates sensitive data (malicious version 9.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in paypal-business-sdk (npm)

MAL-2026-14435

Immediate action

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

npm uninstall paypal-business-sdk

What this malware does

The package's npm preinstall lifecycle script collects the installer's OS username, hostname, current working directory, and walks up to 15 parent directories to read enclosing package.json files (capturing the victim project's name, author, and version). The collected metadata is hex-encoded, chunked into DNS subdomain labels, and exfiltrated via dns.lookup queries under the hardcoded nameserver o.jgl.red (observed label da5u87oh92rc72pp1dngqfc6hp8gwshm6.o.jgl.red). The package name impersonates a PayPal SDK, consistent with a dependency-confusion reconnaissance beacon that fires automatically on npm install.

Malicious versions

1 flagged

9.4.3

Indicators of compromise (SHA-256)

556bfd93652f806523495944dc8a441624c9a2dae4f76eadeefa9650f57091a1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for paypal-business-sdk (version 9.4.3).
If you installed it — respond
paypal-business-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If paypal-business-sdk 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

No. paypal-business-sdk on npm has been identified as a malicious package (version 9.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018635

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks paypal-business-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database