Malicious code in sme-rko-finance-front-payments-domain (npm)
The npm package sme-rko-finance-front-payments-domain contained malicious code that downloads and executes OS-specific binaries from attacker-controlled C2 servers upon require(). The package name was crafted to mimic legitimate internal finance/payments domain naming conventions.
- Disclosed
- Last updated
- Blast radius
- Any developer or application that installed sme-rko-finance-front-payments-domain from npm; runtime execution of arbitrary OS-specific binaries on affected systems.
- Ecosystems
- Attack vectors
- Affected entities
- sme-rko-finance-front-payments-domainnpm package containing malicious code in index.js and ./_polyfill.js
The npm package sme-rko-finance-front-payments-domain was published with embedded malicious code designed to execute arbitrary binaries on systems where the package was installed and required.\n\nUpon require(), the package's index.js loads ./polyfill.js, which reconstructs C2 hostnames from obfuscated string fragments (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) and includes a DNS TXT record fallback via sdk.dl.wel1.ru. The malicious code then downloads OS-specific binaries via HTTPS without signature verification, writes them to temporary directories (/tmp or %TEMP%) with disguised filenames (e.g., .cache or dotnet_diag_.exe), sets executable permissions, and spawns them detached.\n\nThe package name was deliberately crafted to resemble legitimate internal scoped/branded naming for finance and payments domains, likely to evade detection and appear trustworthy to developers.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- sme-rko-finance-front-payments-domain
- Domains
- oob-worker.cf99-9b3.workers.dev
- oob-worker.cf100-416.workers.dev
- oob-worker.cf101-adf.workers.dev
- oob-worker.cf102-baf.workers.dev
- sdk.dl.wel1.ru
Remediation
- Immediately remove sme-rko-finance-front-payments-domain from all package.json files and lock files
- Audit npm install logs and dependency trees to identify all projects that may have installed this package
- Regenerate all credentials, API keys, and secrets on any system where this package was installed and required
- Scan affected systems for the presence of suspicious binaries in /tmp, %TEMP%, and other temporary directories
- Monitor network traffic for connections to the identified C2 domains and DNS queries to sdk.dl.wel1.ru
- Review and update npm security policies to detect and block packages with suspicious naming patterns that mimic internal/scoped naming conventions
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-pmc8-g84p-3x77 · GitHub Advisory Database
Cite this entry
"Malicious code in sme-rko-finance-front-payments-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-payments-domain-npm-pk4lld
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