sme-rko-finance-front-operations-feenpm
sme-rko-finance-front-operations-fee is a confirmed malicious npm package (MAL-2026-13635) 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-fee (npm)
What this malware does
The package's main entry (./lib/telemetry) and its _vendor.js module execute a binary dropper at require/import time. Hostnames and API identifiers are reconstructed from split-string arrays to evade static search — for example ["oob-worker.cf103-070.worke","rs.d","ev"].join("") and require("child_"+"process") / fs["chmod"+"Sync"]. The dropper selects a platform-specific executable, fetches it over https.get from anonymous Cloudflare workers.dev origins (oob-worker.cf103-070.workers.dev, cf100-416.workers.dev, cf99-9b3.workers.dev, cf101-adf.workers.dev), with a base64 DNS-TXT fallback channel over *.dl.wel1.ru (e.g. sdk.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache_<hex> on Linux or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755 is applied, and the file is spawned detached via /bin/sh -c "<path> &" or cmd /c start /b. A parallel dropper path inside lib/telemetry.js performs the same fetch → base64-decode → chmod +x → detached spawn sequence. No pinning, no signature verification, and mutable anonymous hosts. Installing or requiring the package results in remote code execution on the installer's host.
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-fee (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-fee across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-fee 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-fee 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-fee 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-fee-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.