NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

sme-rko-finance-front-operations-feenpm

Advisory published Updated

sme-rko-finance-front-operations-fee is a confirmed malicious npm package (MAL-2026-13635) 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-fee (npm)

MAL-2026-13635
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sme-rko-finance-front-operations-fee

What this malware does

The package's main entry (./lib/telemetry) and its _vendor.js module execute a binary dropper at require/import time. Hostnames and API identifiers are reconstructed from split-string arrays to evade static search — for example ["oob-worker.cf103-070.worke","rs.d","ev"].join("") and require("child_"+"process") / fs["chmod"+"Sync"]. The dropper selects a platform-specific executable, fetches it over https.get from anonymous Cloudflare workers.dev origins (oob-worker.cf103-070.workers.dev, cf100-416.workers.dev, cf99-9b3.workers.dev, cf101-adf.workers.dev), with a base64 DNS-TXT fallback channel over *.dl.wel1.ru (e.g. sdk.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache_<hex> on Linux or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755 is applied, and the file is spawned detached via /bin/sh -c "<path> &" or cmd /c start /b. A parallel dropper path inside lib/telemetry.js performs the same fetch → base64-decode → chmod +x → detached spawn sequence. No pinning, no signature verification, and mutable anonymous hosts. Installing or requiring the package results in remote code execution on the installer's host.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

6a2ef64871ebe6bf7dd675b3e686beec5a90dbaec72760b647e3c876674df9c5

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for sme-rko-finance-front-operations-fee (version 35.8.1).

  2. If you installed it — respond

    Remove sme-rko-finance-front-operations-fee 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.

  3. Did it already run?

    If sme-rko-finance-front-operations-fee was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sme-rko-finance-front-operations-fee on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017160

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sme-rko-finance-front-operations-fee-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
sme-rko-finance-front-operations-fee (npm) malicious package — MAL-2026-13635 | O3 Security