sme-rko-finance-front-operations-sharednpm
sme-rko-finance-front-operations-shared is a confirmed malicious npm package (MAL-2026-13647) 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-shared (npm)
What this malware does
On require/import, index.js loads./bootstrap and re-exports./lib/telemetry, both of which execute a download-and-execute dropper. bootstrap.js reconstructs hardcoded hosts via array-join obfuscation (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, with a DNS-TXT chunked fallback under *.dl.wel1.ru), fetches a platform-specific binary via https.get, writes it to /var/tmp or %TEMP% under a disguised name (.cache<rnd> / dotnet_diag<rnd>.exe), chmods 0o755 on POSIX, and detached-spawns it via cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true}).unref(). Sensitive APIs are also obfuscated (require('child_'+'process'), fs['chmod'+'Sync']) to evade string-based scanners, and markerFresh() rate-limits re-execution. lib/telemetry.js (the module actually exported from index.js) contains a parallel dropper that base64-decodes embedded chunks, writes them to disk, chmods 0o755 via the same obfuscated accessor, and detached-spawns them through /bin/sh. The package presents as "analytics" but ships two independent import-time RCE paths delivering attacker-controlled binaries from anonymous Cloudflare workers.dev endpoints and a Russian lookalike TLD, unpinned and unverified.
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-shared (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-shared across your stack and pipelines.
If you installed it — respond
sme-rko-finance-front-operations-shared is a typosquat — you almost certainly intended a legitimately-named package. Remove sme-rko-finance-front-operations-shared, 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-shared 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-shared 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-shared-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.