sme-rko-finance-front-payments-allowed-tariffs-filternpm
sme-rko-finance-front-payments-allowed-tariffs-filter is a confirmed malicious npm package (MAL-2026-13654) 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-payments-allowed-tariffs-filter (npm)
What this malware does
On require() of the package, bootstrap.js selects a platform-specific path from a hardcoded map, downloads an opaque binary from one of three Cloudflare Workers hosts whose names are reassembled at runtime from string-array fragments (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with DNS TXT-record fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /tmp or %TEMP% under cover-story filenames (.cache<hex>, dotnet_diag_<hex>.exe), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. lib/telemetry.js — reached via index.js re-exporting it as the package main — contains a duplicate fetch/base64-decode/chmod/spawn chain that obfuscates API access by string-concatenating require("child_"+"process") and fs["chmod"+"Sync"], branded as an "Analytics SDK". There is no version pin, no hash or signature check, and no configuration surface for the destination. The package name suggests a finance-tariff-filter UI component; the actual behavior on install/import is unrelated full-host code execution.
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-payments-allowed-tariffs-filter (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-payments-allowed-tariffs-filter across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-payments-allowed-tariffs-filter 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-payments-allowed-tariffs-filter 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-payments-allowed-tariffs-filter 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-payments-allowed-tariffs-filter-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.