sme-rko-finance-front-operations-holding-domainnpm
sme-rko-finance-front-operations-holding-domain is a confirmed malicious npm package (MAL-2026-13638) 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-holding-domain (npm)
What this malware does
On require() of the package, shim.js executes a bootstrap() at module top level that fetches a platform-specific native binary from string-concatenation-obfuscated hosts under oob-worker.cf10{0,1,2}-*.workers.dev, with a base64 DNS-TXT fallback under *.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<rand> (POSIX) or %TEMP%\dotnet_diag_<rand>.exe (Windows), chmod'd 0755, and detached-spawned via /bin/sh -c or cmd /c start /b. The exported main lib/telemetry.js contains a duplicate download-decode-chmod-exec chain (Buffer.from(chunks,'base64'), fs'chmod'+'Sync', cp.spawn('/bin/sh',['-c', filePath + ' &'],{detached:true})) presented under an SDK/telemetry cover story. Destination hostnames and dangerous identifiers (require('child_'+'process'), fs['chmod'+'Sync']) are constructed via array-join and string concatenation to defeat static analysis. Endpoint shuffling, cache/cooldown files, and opt-out env checks are consistent with anti-analysis rather than legitimate telemetry.
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-holding-domain (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-holding-domain across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-holding-domain 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-holding-domain 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-holding-domain 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-holding-domain-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.