sme-rko-finance-front-operations-notifications-modelsnpm
sme-rko-finance-front-operations-notifications-models is a confirmed malicious npm package (MAL-2026-13641) 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-notifications-models (npm)
What this malware does
On require of the package, index.js side-effect loads polyfill.js and lib/telemetry.js, both of which act as native-binary droppers. Hostnames and privileged API names are assembled via array.join('') to evade static scans (e.g. require("child" + "process"), MIRRORS built from ["oob-worker.cf102-baf.worke","rs.d","ev"].join('')). The code downloads a platform-specific binary via https.get from oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf101-adf.workers.dev, with a DNS TXT fallback under *.dl.wel1.ru that base64-reassembles the payload. The fetched bytes are written to /var/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe (masquerading as a dotnet diagnostic file), chmod 0755'd, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or cmd.exe /c start /b. lib/telemetry.js contains a parallel dropper path (base64 chunk assembly, chmodSync to 0755, cp.spawn('/bin/sh',...)) so execution occurs even if _polyfill.js is removed. The declared 'core infrastructure utilities / telemetry' purpose does not match downloading and executing opaque native binaries from anonymous Cloudflare Workers subdomains.
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-notifications-models (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-models across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-notifications-models 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-notifications-models 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-models 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-models-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.