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

@apple-pay-trust/finishnpm

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

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

What this malware does

The package @apple-pay-trust/finish 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.

The OpenSSF Package Analysis project identified '@apple-pay-trust/finish' @ 99.0.3 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
99.0.3

Indicators of compromise (SHA-256)

de7e20491e24083ffe9c02837f52c10ae2b7a7fb0402c8533122afe9fbd9c63e
9abd2d210c4a5df0e95f326e80b2e6618647c03ba4158e1d6ffbd36d9f7b800a
c3fce4bd1b8276028052d43a59f483bb5acacba46ae7e1bc40602184c514c5f0

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 @apple-pay-trust/finish (version 99.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @apple-pay-trust/finish across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-45wm-8rff-vxfr

References

Credits

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

Detect & block this

O3 blocks @apple-pay-trust/finish-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/finish (npm) malicious package — MAL-2026-3114 | O3 Security