Malicious code in sme-rko-finance-front-operations-domain (npm)
The npm package sme-rko-finance-front-operations-domain contained malicious code that downloads and executes platform-specific native binaries from attacker-controlled servers. The package uses obfuscation techniques to evade detection and includes DNS-TXT fallback channels to bypass HTTP egress controls.
- Disclosed
- Last updated
- Blast radius
- Any developer or application that installed sme-rko-finance-front-operations-domain from npm and executed it.
- Ecosystems
- Attack vectors
- Affected entities
- sme-rko-finance-front-operations-domainnpm package containing malicious code
The npm package sme-rko-finance-front-operations-domain was found to contain malicious code that executes automatically upon require. The index.js file loads shim.js, which contains an async initializer that assembles platform-specific hostnames from split-string arrays to target attacker-controlled endpoints: oob-worker.cf102-baf.workers.dev and sdk/ext/pkg/net.dl.wel1.ru.\n\nThe malicious code downloads native binaries over HTTPS and writes them to temporary directories (/tmp or %TEMP%) under disguised names such as .cache or dotnet_diag_.exe. The files are then made executable (chmod 0755) and spawned detached via shell commands (/bin/sh -c or cmd.exe /c start /b). A secondary execution path exists in lib/telemetry.js, presented as an observability/Sentry-like SDK, which contains identical dropper primitives.\n\nTo evade static analysis, child_process, chmodSync, and endpoint hostnames are reconstructed at runtime from concatenated string fragments. The fetched binaries are unsigned and unverifiable, with no integrity checks or pinned publisher-owned sources. A DNS-TXT fallback channel (dns.resolveTxt) reassembles and base64-decodes payloads when HTTPS retrieval fails, allowing the attack to bypass HTTP egress controls.\n\nThe malicious package was identified by the OpenSSF malicious-packages project and reported via GitHub Security Advisory GHSA-4rj4-828w-hv35."
Indicators of compromise
- Packages
- sme-rko-finance-front-operations-domain
- Domains
- oob-worker.cf102-baf.workers.dev
- sdk/ext/pkg/net.dl.wel1.ru
Remediation
- Immediately remove sme-rko-finance-front-operations-domain from all projects and dependencies
- Audit npm package.json and lock files for any presence of this package
- Review and revoke any credentials or secrets that may have been exposed on systems where this package was installed
- Inspect system logs and process execution history on affected machines for signs of binary downloads and execution from the attacker-controlled domains
- Block outbound connections to oob-worker.cf102-baf.workers.dev and sdk/ext/pkg/net.dl.wel1.ru at the network level
- Monitor for DNS queries to the fallback DNS-TXT channels mentioned in the malicious code
- Update npm to the latest version and run npm audit to detect similar compromised packages
Sources
- GitHub Advisory GHSA-4rj4-828w-hv35 · GitHub Advisory Database
Cite this entry
"Malicious code in sme-rko-finance-front-operations-domain (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 8, 2026; last updated August 8, 2026. https://supplychainattack.org/incident/malicious-code-in-sme-rko-finance-front-operations-domain-npm-cz7dfq
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting