sme-rko-finance-front-operations-penaltynpm
sme-rko-finance-front-operations-penalty is a confirmed malicious npm package (MAL-2026-13645) 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-penalty (npm)
What this malware does
On require() of the package, runtime.js and lib/telemetry.js reassemble Cloudflare Workers hostnames (oob-worker.cf103-07/cf99-9b3/cf100-416/cf101-adf.workers.dev) from split string arrays, fetch a platform-specific binary from /pkg/package[-arm64|.exe|loader_mac], write it to /var/tmp/.cache<uid> on Unix or %TEMP%\dotnet_diag_<uid>.exe on Windows, chmod 0755, and spawn it detached via /bin/sh -c or cmd.exe. A DNS TXT chunked-base64 fallback channel to .dl.wel1.ru is used when HTTPS fails. Obfuscation techniques include string-split concatenation of host names, dynamic require("child_" + "process"), bracket-notation fs["chmod" + "Sync"], and disguised filenames masquerading as system diagnostics (dotnet_diag,.analytics_state,.cache_). Both the auxiliary _runtime.js and the main entrypoint lib/telemetry.js reachable via index.js contain the dropper primitives, ensuring execution on import.
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-penalty (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-penalty across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-penalty 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-penalty 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-penalty 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-penalty-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.