Which versions of @apple-pay-trust/destroy are malicious?

The following npm versions of @apple-pay-trust/destroy are flagged malicious: 99.0.1, 99.0.2, 99.0.3, 99.0.4. Treat any of these as compromised.

How do I remediate @apple-pay-trust/destroy if I installed it?

@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.

I already installed @apple-pay-trust/destroy — how do I know if it already compromised me?

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.

Is @apple-pay-trust/destroy part of a known attack campaign?

Yes — @apple-pay-trust/destroy is associated with the GHSA-r239-hc6j-wmm8, RLMA-2026-04666 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @apple-pay-trust/destroy across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @apple-pay-trust/destroy (4 malicious 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.

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

4 flagged

99.0.199.0.299.0.399.0.4

Indicators of compromise (SHA-256)

fd2be309fcd255b143b67b7c286a5a662737d86bf2dcb2dc1b327cb770defb77

6515019a886959d905d728f0fdcebeb16aa3e62bcf2e2643c0424ba87aeb8f79

ffafff9d3e86c7cc3e58e4f14f04286e6e0d5ca4a5c32707266627f652350d1e

Detection & response playbook

Destructive / sabotage

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 (4 malicious 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.
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.
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.
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 (versions 99.0.1, 99.0.2, 99.0.3, 99.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r239-hc6j-wmm8RLMA-2026-04666

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · 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.

Malware detection Runtime egress monitoring