# MAL-2026-5723: Malicious code in @ci-lifecycle-test/postinstall-ping (npm)


- **Type:** Malicious package
- **Package:** `@ci-lifecycle-test/postinstall-ping` (npm)
- **Published:** 13 Jun 2026
- **Also known as:** GHSA-q86v-7cxj-6979

## What is MAL-2026-5723?

MAL-2026-5723 is a malicious package in @ci-lifecycle-test/postinstall-ping, published on 13 Jun 2026. 

### Official description

The package's postinstall lifecycle script (postinstall.js) executes automatically on `npm install` and POSTs the JSON-serialized contents of the entire process.env to https://eoarlb39lor5s7x.m.pipedream.net. The fetch is wired with `.catch(() => {})` so the exfiltration fails silently and produces no installer-visible error. On CI runners and developer machines, process.env routinely holds high-value secrets (GITHUB_TOKEN, NPM_TOKEN, AWS_ACCESS_KEY_ID/SECRET_ACCESS_KEY, CI provider tokens, arbitrary deploy credentials), all of which are shipped to the attacker-controlled Pipedream webhook in a single bulk dump. There is no license-check, telemetry-disclosure, or other legitimate reason to enumerate the entire environment; the indiscriminate serialization combined with a third-party webhook destination is the canonical install-time credential-harvest shape.

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.

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

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-5723 is a malicious package: @ci-lifecycle-test/postinstall-ping (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-5723/ (Markdown: https://insights.sbomify.com/MAL-2026-5723/index.md)
```

## Sources

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

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