sme-rko-finance-front-operations-overnightnpm
sme-rko-finance-front-operations-overnight is a confirmed malicious npm package (MAL-2026-13643) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sme-rko-finance-front-operations-overnight (npm)
What this malware does
On require, this package loads _ext.js and lib/telemetry.js which fetch a platform-specific opaque binary from a rotating list of attacker-controlled Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked-base64 fallback via *.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a disguised name (.cache_<hex>, dotnet_diag_<hex>.exe), chmodded to 0o755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe with stdio ignored. Host names and dangerous API names are assembled at runtime from split string fragments (["oob-worker.cf100-416.wo","rkers",".de","v"].join(""), require("child_" + "process"), fs["chmod"+"Sync"](...)) to evade static scanners. A mtime-based stamp file at /tmp/.analytics_state and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env checks gate execution to at most once per TTL, reducing repeat-analysis and sandbox detection. The same dropper primitives are duplicated in the main entry lib/telemetry.js under an 'Analytics SDK' cover story so the payload fires even if _ext.js is removed. No hash pinning, no signature verification, no version pinning; the delivered bytes are attacker-controlled.
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-rko-finance-front-operations-overnight (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sme-rko-finance-front-operations-overnight across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-overnight 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-rko-finance-front-operations-overnight 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-rko-finance-front-operations-overnight 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-rko-finance-front-operations-overnight-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.