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

post-purchase-bundlernpm

Malicious code in post-purchase-bundler (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3412
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall post-purchase-bundler

What this malware does

The package post-purchase-bundler was found to contain malicious code.

The OpenSSF Package Analysis project identified 'post-purchase-bundler' @ 99.9.25 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
99.9.999.9.25

Indicators of compromise (SHA-256)

e9f3292f2f19840d6a3685add8754353fcf47bd9240b53ab5552b6a716254e7a
6ee91ffff812d05531df7ad59d39eb10a0db8bf0ed97263701d772f4a5429e60
3a33aa69ef958573a786f3db208d8ee335829e14009d1fdafecbc842ed493b8b

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for post-purchase-bundler (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging post-purchase-bundler across your stack and pipelines.

  2. If you installed it — respond

    Remove post-purchase-bundler from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If post-purchase-bundler 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 post-purchase-bundler 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. post-purchase-bundler on npm has been identified as a malicious package (versions 99.9.9, 99.9.25 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks post-purchase-bundler-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

post-purchase-bundler (npm) malicious package — MAL-2026-3412 | O3 Security