sme-rko-finance-front-operations-providersnpm
sme-rko-finance-front-operations-providers is a confirmed malicious npm package (MAL-2026-13646) 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-providers (npm)
What this malware does
On require() of the package, index.js loads bridge.js which assembles Cloudflare Workers subdomain hostnames from split string fragments (oob-worker.cf103-070.workers.dev, cf100-416, cf101-adf.workers.dev) and downloads a platform-specific binary via https.get. The fetched bytes are written to a decoy path under /tmp or %TEMP% (.cache<hex>/dotnet_diag_<hex>.exe), chmod 0755 on Unix, and executed detached via spawn("/bin/sh",["-c", fp+" &"]) or spawn("cmd",...) on Windows. A DNS-TXT fallback channel resolves shards from wel1.ru (sdk.dl.wel1.ru assembled from fragments) — a count record c.<domain> followed by numeric shards <i>.<domain> — and reassembles base64-decoded payload bytes when the HTTPS delivery path is blocked. Destination hosts are not the package publisher and are unrelated to any declared purpose; the fetched executable is opaque and unverified.
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-providers (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-providers across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-providers 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-providers 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-providers 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-providers-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.