sme-scripts-clinpm
sme-scripts-cli is a confirmed malicious npm package (MAL-2026-12208) that executes malicious code on install (malicious version 20.5.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sme-scripts-cli (npm)
What this malware does
On require('sme-scripts-cli'), index.js loads bridge.js which detects OS/architecture, downloads an OS-specific binary from hardcoded Cloudflare workers.dev endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT fallback via *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), writes the payload to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd. Endpoint hostnames and API names are reconstructed at runtime by joining split string fragments (['oo','b-worke','r.cf100-416.wor','ke','rs.de','v'].join('')) to evade static analysis. No hash or signature verification is performed on the downloaded binary. A second variant of the dropper is bundled at lib/telemetry.js disguised as a 'tracing.node' analytics SDK, with base64-chunk decoding of network content and identical spawn+chmod primitives.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sme-scripts-cli (version 20.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sme-scripts-cli across your stack and pipelines.
If you installed it — respond
Remove sme-scripts-cli 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.
Did it already run?
If sme-scripts-cli 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 sme-scripts-cli 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sme-scripts-cli-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.