sme-rko-finance-front-operations-othernpm
sme-rko-finance-front-operations-other is a confirmed malicious npm package (MAL-2026-13642) 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-other (npm)
What this malware does
On require()/import, init.js selects an OS/arch-specific binary and downloads it from a rotating set of Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written under disguised names (dotnet_diag.exe,.cache_) to /var/tmp or Windows TEMP, chmod'd 0755, and spawned detached via /bin/sh or cmd. A second dropper in lib/telemetry.js (loaded as the main export inside a decoy Sentry-like SDK bundle) base64-decodes downloaded bytes, chmods 0755 via a dynamically constructed property name ("chmod"+"Sync"), and spawns the resulting file detached. Hostnames and dangerous API names are assembled from split string fragments at runtime ("child_"+"process",.join("") over host fragments) to defeat static analysis. No pinning, no hash or signature verification, and the delivered content is opaque and unrelated to any documented package purpose.
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-other (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-other across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-other 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-other 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-other 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-other-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.