Which versions of grateful-checkout are malicious?

The following npm versions of grateful-checkout are flagged malicious: 99.0.0-canary.1. Treat any of these as compromised.

How do I remediate grateful-checkout if I installed it?

Remove grateful-checkout 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is grateful-checkout part of a known attack campaign?

Yes — grateful-checkout is associated with the IN-MAL-2026-005118, IN-MAL-2026-005117 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect grateful-checkout in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking grateful-checkout and packages like it before any post-install script runs.

Malicious package

grateful-checkoutnpm

Malicious code in grateful-checkout (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5444

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall grateful-checkout

What this malware does

On npm install, the postinstall hook in src/canary.js performs a DNS lookup and an HTTPS GET to a serveo tunnel host (96e03fa6c292469a-172-245-86-254.serveousercontent.com/canary-install?pkg=...&ver=...), leaking the installer's source IP and the resolved package name/version to a third-party endpoint without consent. The package's README falsely claims that no data is collected or transmitted. The package additionally impersonates the API surface of an internal Exodus checkout-signing module (generateMnemonicSigningKeys, signDirectPaymentMultiChain, signCapture, signRefund, signCharge, signCancelSubscription) to land via dependency confusion against private name resolution. While self-described as a security research PoC, the behavior — uncontracted outbound network from a lifecycle hook to a researcher-controlled tunnel and namespace impersonation of a private package — is installer-harming regardless of intent.

Malicious versions

1 flagged

99.0.0-canary.1

Indicators of compromise (SHA-256)

09b2768ea8a2c0f9038e40a8109ae744ca38de664099bfa1fdf128790baeb67d

c2a9600ad3ee3fddd9f06425260c94edf660263800080787155a63d3e5212d12

Frequently asked questions

No. grateful-checkout on npm has been identified as a malicious package (version 99.0.0-canary.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005118IN-MAL-2026-005117

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection