# MAL-2026-11062: Malicious code in preferenceslifecycle-paypal (npm)


- **Type:** Malicious package
- **Package:** `preferenceslifecycle-paypal` (npm)
- **Published:** 25 Jul 2026
- **Also known as:** GHSA-jpjh-7qpg-hqxv

## What is MAL-2026-11062?

MAL-2026-11062 is a malicious package in preferenceslifecycle-paypal, published on 25 Jul 2026. 

### Official description

The package's preinstall hook executes index.js, which collects host identifiers (os.hostname(), os.platform(), os.arch(), os.homedir(), and dns.getServers()) and POSTs them as JSON to the hardcoded host ucahu2x3m2osjmwim8n8vmn1ssykmnac.oastify.com (a Burp Collaborator out-of-band domain) at /hit. The transmission is unconditional and fires automatically on npm install without any documented purpose or opt-in. The package name resembles internal-package/scope conventions, matching a dependency-confusion beaconing pattern where install-time execution confirms resolution of an attacker-published lookalike inside a target environment.

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 'preferenceslifecycle-paypal' @ 28.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

## What should I do about MAL-2026-11062?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11062 is a malicious package: preferenceslifecycle-paypal (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11062/ (Markdown: https://insights.sbomify.com/MAL-2026-11062/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11062

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11062/
Summaries are generated and may contain mistakes; the official description above is the record.