sme-rko-finance-front-operations-incomenpm
sme-rko-finance-front-operations-income is a confirmed malicious npm package (MAL-2026-13639) 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-income (npm)
What this malware does
On require of the package, compat.js reconstructs attacker-controlled hostnames via array split-and-join obfuscation (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, and sdk/ext/pkg/net.dl.wel1.ru), downloads a platform-specific native executable over HTTPS, writes it to /var/tmp under a hidden dotfile name on Unix or to the Windows temp directory as dotnet_diag<hex>.exe, chmods it to 0755, and spawns it detached via /bin/sh -c or cmd /c start. A fallback retrieval path resolves DNS TXT records at c.<domain> and N.<domain>, base64-decodes and reassembles the chunks into the same executable blob, and writes it to disk for execution — a covert delivery channel that bypasses HTTPS-based network filtering. The package is advertised as a monitoring/observability SDK but ships no functionality matching that purpose; the sole import-time effect is dropping and running an opaque author-controlled binary. Hostname obfuscation via.join(''), masquerade filenames imitating.NET diagnostics tooling, detached spawn, and a DNS-TXT covert channel are consistent with a supply-chain remote code execution dropper.
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-income (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-income across your stack and pipelines.
If you installed it — respond
Remove sme-rko-finance-front-operations-income 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-income 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-income 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-income-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.