sme-rko-finance-front-operations-notifications-implnpm
sme-rko-finance-front-operations-notifications-impl is a confirmed malicious npm package (MAL-2026-13640) 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-operations-notifications-impl (npm)
What this malware does
On require(), index.js loads adapter.js which selects a platform-specific payload (linux x64/arm64, darwin, win32) and fetches it from string-split-obfuscated hosts including oob-worker.cf1-01-adf.workers.dev and sdk.dl.wel1.ru, with a DNS-TXT fallback over *.dl.wel1.ru. The retrieved bytes are written to a hidden temp file, chmodded to 0755 on POSIX, and executed detached via spawn("/bin/sh", ["-c", filePath + " &"]) or spawn("cmd",...) on Windows. A second parallel dropper exists in the package's main module lib/telemetry.js under an 'analytics SDK' cover story, reproducing the base64/DNS-TXT decode, chmod 0755, and /bin/sh execution path. Hostnames and the string 'child_process' are assembled at runtime from split arrays (e.g. require("child" + "process"), ['sdk.dl.wel1.ru'].join(""), ['ext.dl.we','l1.','ru'].join("")) to evade static detection. No signature or hash verification is performed; destinations are not the declared publisher's infrastructure. The package name mimics an internal-looking scope (sme-rko-finance-front-operations-notifications-impl) consistent with a dependency-confusion lure.
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-operations-notifications-impl (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-notifications-impl across your stack and pipelines.
If you installed it — respond
sme-rko-finance-front-operations-notifications-impl is a typosquat — you almost certainly intended a legitimately-named package. Remove sme-rko-finance-front-operations-notifications-impl, 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-operations-notifications-impl 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-notifications-impl 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-notifications-impl-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.