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

@apple-pay-trust/destroynpm

Malicious code in @apple-pay-trust/destroy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3317
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @apple-pay-trust/destroy

What this malware does

The package @apple-pay-trust/destroy was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

fd2be309fcd255b143b67b7c286a5a662737d86bf2dcb2dc1b327cb770defb77
6515019a886959d905d728f0fdcebeb16aa3e62bcf2e2643c0424ba87aeb8f79

Detection & response playbook

Destructive / sabotage
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @apple-pay-trust/destroy (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @apple-pay-trust/destroy across your stack and pipelines.

  2. If you installed it — respond

    @apple-pay-trust/destroy carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

  3. Did it already run?

    If @apple-pay-trust/destroy 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 @apple-pay-trust/destroy 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. @apple-pay-trust/destroy on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r239-hc6j-wmm8

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @apple-pay-trust/destroy-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.

@apple-pay-trust/destroy (npm) malicious package — MAL-2026-3317 | O3 Security