Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in sme-rko-finance-front-operations-other (npm)

The npm package sme-rko-finance-front-operations-other contained malicious code that downloads and executes arbitrary OS-specific binaries from attacker-controlled infrastructure on require/import. The package used obfuscation techniques to evade static analysis and included no signature verification.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any application that installed sme-rko-finance-front-operations-other; runtime code execution on require/import with arbitrary binary download and execution.
Ecosystems
Attack vectors
Affected entities
  • sme-rko-finance-front-operations-othernpm package containing malicious dropper code

The npm package sme-rko-finance-front-operations-other was found to contain malicious code designed to download and execute arbitrary binaries. The attack was discovered via Amazon Inspector and credited to the OpenSSF malicious-packages project.\n\nThe malicious payload is distributed across two files: init.js and lib/telemetry.js. On require() or import, init.js selects an OS/architecture-specific binary and downloads it from a rotating set of Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT fallback mechanism using domains under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to temporary directories (/var/tmp on Unix, Windows TEMP on Windows) under disguised filenames (dotnet_diag*.exe, .cache*), made executable (chmod 0755), and spawned detached via /bin/sh or cmd.\n\nA second dropper in lib/telemetry.js, loaded as the main export within a decoy Sentry-like SDK bundle, base64-decodes downloaded bytes, applies executable permissions via dynamically constructed property names, and spawns the resulting file detached. The package employed runtime string obfuscation (e.g., concatenating fragments like "child_"+"process") to defeat static analysis. No cryptographic pinning, hash verification, or signature validation was present, and the delivered content bore no relation to any documented package purpose.\n\nThe package was identified and reported through the OpenSSF malicious-packages repository.

Indicators of compromise

Domains
  • oob-worker.cf103-070.workers.dev
  • oob-worker.cf102-baf.workers.dev
  • oob-worker.cf100-416.workers.dev
  • sdk.dl.wel1.ru
  • ext.dl.wel1.ru
  • pkg.dl.wel1.ru
  • net.dl.wel1.ru

Remediation

  • Immediately uninstall sme-rko-finance-front-operations-other from all projects and environments
  • Audit npm package.lock or yarn.lock files to identify all installations of this package
  • Review process execution logs and network traffic for any suspicious binary downloads or executions from the identified domains
  • Regenerate any credentials or secrets that may have been exposed on affected systems
  • Update to a safe version if a legitimate replacement package is available, or use an alternative package
  • Implement npm package scanning and verification in CI/CD pipelines to detect malicious packages before installation
  • Monitor for any outbound connections to the identified Cloudflare Workers and wel1.ru domains

Sources

  1. GitHub Advisory GHSA-xqr4-4gx9-7w24 · GitHub Advisory Database

Cite this entry

"Malicious code in sme-rko-finance-front-operations-other (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-other-npm-yo1zo0

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. 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
  2. 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
  3. 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
  4. 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