sme-rko-finance-front-payment-registers-operations-domainnpm
sme-rko-finance-front-payment-registers-operations-domain is a confirmed malicious npm package (MAL-2026-13653) that typosquats a legitimate package to trick installs (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sme-rko-finance-front-payment-registers-operations-domain (npm)
What this malware does
index.js unconditionally loads runtime.js on require. runtime.js detects the host OS and architecture, then downloads an opaque platform-matched binary over HTTPS from hardcoded Cloudflare workers.dev subdomains (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev). If HTTPS retrieval fails, it falls back to a DNS-TXT covert channel under *.dl.wel1.ru, requesting a chunk-count TXT record at c.<domain> and then reassembling base64-encoded payload chunks from N.<domain> TXT queries. The reassembled bytes are written to /var/tmp or %TEMP% under a disguised filename (.cache<rand> or dotnet_diag<rand>.exe mimicking a.NET diagnostic tool), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Both the CDN hostnames and the fallback resolver domains are constructed by Array.join of split fragments to evade string scanning. The delivered binary is unpinned, unverified, opaque, and served from anonymous edge-worker infrastructure and a.ru DNS channel unrelated to any legitimate publisher of a finance/payment-registers package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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-payment-registers-operations-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-payment-registers-operations-domain across your stack and pipelines.
If you installed it — respond
sme-rko-finance-front-payment-registers-operations-domain is a typosquat — you almost certainly intended a legitimately-named package. Remove sme-rko-finance-front-payment-registers-operations-domain, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If sme-rko-finance-front-payment-registers-operations-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-payment-registers-operations-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-payment-registers-operations-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.