sme-rko-finance-front-operations-special-paymentsnpm
sme-rko-finance-front-operations-special-payments is a confirmed malicious npm package (MAL-2026-13648) that opens a backdoor for remote access (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-special-payments (npm)
What this malware does
On require() of the package, index.js loads support.js which downloads a platform-specific binary from string-concatenated cloudflare workers.dev subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS TXT chunked-transfer fallback to *.dl.wel1.ru. The payload is written to /tmp with a hidden name (.cache<hex>) or to %TEMP% as dotnet_diag_<hex>.exe on Windows, chmodded 0755, and spawned detached via /bin/sh -c or cmd. The declared main module lib/telemetry.js contains a duplicate dropper path under an 'analytics SDK' cover story, base64-decoding transport chunks before executing the resulting binary the same way. C2 host names and dangerous API names (child_process, chmodSync) are constructed at runtime via array-join and string concatenation to defeat static analysis. Both dropper paths fire at library load time on any require of the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind 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-special-payments (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-special-payments across your stack and pipelines.
If you installed it — respond
sme-rko-finance-front-operations-special-payments establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sme-rko-finance-front-operations-special-payments 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-special-payments 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-special-payments-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.