What does the switchpaymentsapiserv-paypal malware do?

The package's preinstall lifecycle script runs automatically on npm install and exfiltrates installer identity data via DNS. It collects os.userInfo().username, os.hostname(), and process.cwd(), JSON-serializes the values, hex-encodes them, chunks the hex into DNS-label-sized fragments, and issues dns.lookup queries of the form ` . . .d9jfvjgl8o8s72utl810ktk61s1xmsysr.o.jgl.red`. The attacker-controlled authoritative nameserver for `*.o.jgl.red` reconstructs the payload from the query stream. Using DNS as the exfiltration channel bypasses typical HTTP egress controls and proxy logging. The in-code comment labeling the data as 'non-sensitive' does not match the behavior, which

Which versions of switchpaymentsapiserv-paypal are malicious?

The following npm versions of switchpaymentsapiserv-paypal are flagged malicious: 2.3.4. Treat any of these as compromised.

How do I remediate switchpaymentsapiserv-paypal if I installed it?

switchpaymentsapiserv-paypal 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 switchpaymentsapiserv-paypal — how do I know if it already compromised me?

If switchpaymentsapiserv-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.

Is switchpaymentsapiserv-paypal part of a known attack campaign?

Yes — switchpaymentsapiserv-paypal is associated with the GHSA-rg3f-q822-6rx6, IN-MAL-2026-011081 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 switchpaymentsapiserv-paypal 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 switchpaymentsapiserv-paypal (version 2.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging switchpaymentsapiserv-paypal across your stack and pipelines.

Malicious package

switchpaymentsapiserv-paypalnpm

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

Malicious code in switchpaymentsapiserv-paypal (npm)

MAL-2026-11392

Immediate action

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

npm uninstall switchpaymentsapiserv-paypal

What this malware does

The package's preinstall lifecycle script runs automatically on npm install and exfiltrates installer identity data via DNS. It collects os.userInfo().username, os.hostname(), and process.cwd(), JSON-serializes the values, hex-encodes them, chunks the hex into DNS-label-sized fragments, and issues dns.lookup queries of the form <index>.<chunk>.<tag>.d9jfvjgl8o8s72utl810ktk61s1xmsysr.o.jgl.red. The attacker-controlled authoritative nameserver for *.o.jgl.red reconstructs the payload from the query stream. Using DNS as the exfiltration channel bypasses typical HTTP egress controls and proxy logging. The in-code comment labeling the data as 'non-sensitive' does not match the behavior, which is covert transmission of host, user, and filesystem-path identifiers to a non-first-party domain at install time.

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

1 flagged

2.3.4

Indicators of compromise (SHA-256)

12fb976a9e7017cbd4a87769d48e213d81eb350767ba2ab4b7d8653501215daa

cdf45ca375c6a15e134abf2ab456c8cbd75e514d934e2c16b1d2b23e9677186a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for switchpaymentsapiserv-paypal (version 2.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging switchpaymentsapiserv-paypal across your stack and pipelines.
If you installed it — respond
switchpaymentsapiserv-paypal 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 switchpaymentsapiserv-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 switchpaymentsapiserv-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

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

Campaign

GHSA-rg3f-q822-6rx6IN-MAL-2026-011081

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks switchpaymentsapiserv-paypal-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