L3 · Shartednpm · Supply chain · Malwarecherry-miniapp-sdk-malware

GitHub flags two @cherrydotfun/miniapp-sdk npm releases as malware

GitHub lists @cherrydotfun/miniapp-sdk 0.1.22 and 0.1.23 as malware. npm lists 0.1.21 as latest and omits both affected releases from its version list. Identify installations from lockfiles and build logs, isolate exposed environments and rotate their secrets. GitHub lists no patched version.

Disclosed: Nov 6, 2026; Public disclosure date
Severity: Sharted; 1 CVE tracked here
Splash zone: Developer machines and CI workers that installed or ran @cherrydotfun/miniapp-sdk 0.1.22 or 0.1.23.; npm
In the wild: Unknown; Malicious packages were published. Confirmed downstream victims have not been disclosed.

What happened

The advisory establishes two malicious versions of the published SDK. The public sources reviewed do not establish how the releases were published, which credentials the code reached, or who ran it. Treat systems that installed or ran either version as potentially compromised. Removing the dependency alone cannot clear a host.

The registry currently advertises 0.1.21 as latest and no longer includes metadata for the two versions in its version map. Publication timestamps remain visible. Review prior installations and cached artifacts even if a fresh registry lookup no longer offers those versions.

What’s in the bowl

GHSA-q8jp-gq6p-hwpx

Malicious npm releases

GitHub marks exactly 0.1.22 and 0.1.23 as malware and lists no patched release.

Crime-scene timeline

Nov 6, 20:46–21:36 UTC
Two affected npm releases appear
Registry timestamps place 0.1.22 at 20:46 UTC and 0.1.23 at 21:36 UTC.
Nov 6, 22:15 UTC
GitHub publishes its malware advisory
The advisory initially identified 0.1.22.
Nov 6, 23:04 UTC
GitHub adds 0.1.23
The updated advisory lists both versions and no patched release.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.

GitHub malware advisoryPrimaryIdentifies both malicious versions, no patch and the need for host investigation and credential rotation.
npm registry metadataPrimaryRecords both publication times and the current latest tag at 0.1.21.
OpenSSF OSV malware entryPrimaryPreserves the GitHub advisory versions and timestamps. This is an import of the same advisory.

Wipe guide

The wipe checklist

0 of 3 sheets used

Stop affected installations and preserve evidenceSearch npm, pnpm and Yarn lockfiles, SBOMs, package caches and CI logs for the exact package and versions 0.1.22 and 0.1.23. Retain affected build logs and lockfiles. A dependency declaration or cached artifact alone does not prove the code ran.
Isolate machines and workers that installed or ran the releasesPreserve relevant process and network logs before wiping. From a clean device, revoke or rotate accessible registry tokens, CI and cloud credentials, signing keys and other secrets. Inspect related registry publications and CI changes made with those credentials.
Rebuild with a verified dependency setRemove the affected versions, review direct and transitive dependencies, and rebuild on clean infrastructure. Invalidate contaminated caches and replace affected artifacts. Review the provenance of any replacement, including 0.1.21, before pinning it.