Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@ci-lifecycle-test/postinstall-pingnpm

@ci-lifecycle-test/postinstall-ping is a confirmed malicious npm package (MAL-2026-5723) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ci-lifecycle-test/postinstall-ping (npm)

MAL-2026-5723
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ci-lifecycle-test/postinstall-ping

What this malware does

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

47c5e4ee38e9d87c1968c83d8998cb9832d2e72445558ac35217671f1f61d64b
75c160ad40a237c1e682c696ebd0aec2861ca072f47bd5b725bc80f7f95ed509
7bd6753736669af267689cca251d940e02064857c4f134c184b27464f3220aef

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ci-lifecycle-test/postinstall-ping (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ci-lifecycle-test/postinstall-ping across your stack and pipelines.

  2. If you installed it — respond

    @ci-lifecycle-test/postinstall-ping 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.

  3. Did it already run?

    If @ci-lifecycle-test/postinstall-ping 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.

  4. How O3 protects you

    O3 blocks @ci-lifecycle-test/postinstall-ping 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. @ci-lifecycle-test/postinstall-ping on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006274IN-MAL-2026-006273GHSA-q86v-7cxj-6979

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @ci-lifecycle-test/postinstall-ping-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@ci-lifecycle-test/postinstall-ping (npm) malicious package — MAL-2026-5723 | O3 Security