The npm package sme-rko-finance-front-operations-providers version 35.8.1 contains malicious code that, upon require(), downloads and executes an opaque platform-specific binary from suspicious Cloudflare Workers subdomains. It writes the binary to temporary directories, sets executable permissions on Unix, and runs it detached via shell commands. If HTTPS delivery is blocked, a DNS-TXT fallback channel reconstructs the payload from base64-encoded shards resolved from a suspicious domain (wel1.ru). The downloaded executable is unrelated to the package's declared purpose and is unverified, indicating malicious intent.
The npm package 'sme-rko-finance-front-payments-feed-display-list' version 35.8.1 contains malicious code that downloads and executes platform-specific binaries without verification. It dynamically constructs URLs to fetch executables from anonymous worker subdomains, writes them to temporary files with decoy names, sets executable permissions, and runs them detached. If the HTTP fetch fails, it falls back to reconstructing the payload from DNS TXT records. This behavior is inconsistent with the package's benign finance-related name and indicates malicious intent.
The npm package sme-rko-finance-front-operations-overnight version 35.8.1 contains malicious code that loads and executes an attacker-controlled binary from multiple Cloudflare Workers hosts. This binary is fetched dynamically using obfuscated code to evade detection, saved to temporary directories under disguised names, given executable permissions, and run detached from the main process. Execution is gated by environment variables and timestamp files to reduce detection and repeated execution. The malicious payload is embedded in multiple entry points, ensuring execution even if some files are removed. No integrity checks or version pinning are implemented, allowing attackers to control the delivered payload.
The npm package sme-rko-finance-front-payment-registers-operations-domain version 35.8.1 contains malicious code that loads a runtime script which downloads an opaque platform-specific binary from hardcoded Cloudflare workers.dev subdomains. If the HTTPS download fails, it uses a covert DNS-TXT channel to retrieve and reassemble the payload. The binary is saved under disguised filenames in temporary directories, given executable permissions, and executed detached from the main process. The binary is unverified and served from anonymous infrastructure unrelated to the legitimate package publisher.
The npm package sme-rko-finance-front-operations-feed-impl version 35.8.1 contains malicious code that downloads and executes platform-specific binary payloads. It assembles Cloudflare Workers hostnames at runtime to retrieve these payloads, which it writes to temporary directories with disguised filenames and executes detached from the main process. If HTTPS retrieval fails, it uses a DNS TXT record-based staging channel to reconstruct and execute a base64-encoded payload. The malicious module disguises itself as a telemetry SDK and uses obfuscation techniques such as splitting require statements and property names. Both _adapter.js and lib/telemetry.js contain redundant dropper code that executes upon import.
The npm package sme-rko-finance-front-operations-feed-models version 35.8.1 contains malicious code that downloads and executes attacker-controlled native binaries. Upon loading, it unconditionally requires a runtime script that selects a platform-specific endpoint and downloads a binary payload over HTTPS from obfuscated hosts. The payload is saved under decoy filenames mimicking dotnet diagnostic tools and executed with elevated permissions. This behavior is designed to evade static analysis and limit execution frequency. No official patch or remediation guidance is currently available.
The npm package delivery-ci-codeceptjs version 35.1.7 contains malicious code that downloads and executes opaque native binaries from obfuscated Cloudflare Workers subdomains and DNS-TXT record fallbacks. The package's main entry triggers a setup routine that fetches these binaries, writes them to hidden temporary files, sets executable permissions, and runs them detached from the main process. The package itself advertises a trivial no-op class and lacks native source code consistent with the downloaded payload. The obfuscation techniques and fallback mechanisms are designed to evade static detection and blend with normal system activity.
The npm package dolyame-ui-inputautocomplete version 35.8.1 contains malicious code that executes attacker-controlled native binaries upon require/import. It downloads platform-specific native payloads from obfuscated author-controlled hosts and uses DNS TXT record enumeration to reconstruct a fallback payload. The payload is saved to temporary directories and executed with the installer's privileges, employing anti-analysis techniques such as string splitting and filename masquerading.
The devplatform-spa-plugin-remote-module npm package version 35.9.6 contains malicious code that downloads and executes a platform-specific binary from obfuscated external hosts. The binary is saved to temporary directories with disguised names, given executable permissions, and launched detached from the main process. The code uses runtime string reconstruction to evade static analysis. A secondary module includes similar dropper functionality bundled as a payload.
The npm package dolyame-ui-checkablegroup contains malicious code that executes a dropper upon being required. This dropper dynamically constructs obfuscated hostnames to download a binary payload, which it saves under spoofed Microsoft diagnostic tool names and executes detached on the host system. It also uses a covert DNS-TXT fallback channel to receive additional payload data. No integrity verification of the downloaded payload is performed. This behavior is consistent with malware disguised as a UI helper package.
The npm package delivery-ci-jira version 35.5.2 contains malicious code that fetches and executes an opaque binary from obfuscated Cloudflare Workers hosts and fallback DNS TXT records. This binary is written to a temporary path with disguised filenames, given execute permissions, and spawned detached from the main process. The package uses string splitting and environment variable gating to evade static analysis and telemetry detection. The malicious payload is unrelated to the package's stated purpose as a CI/Jira adapter.
The npm package dolyame-ui-progressline version 35.8.1 contains malicious code that, upon being required, downloads and executes platform-specific binaries from hardcoded Cloudflare Workers endpoints or via DNS TXT record fallback. The payload is saved to temporary locations with deceptive names, given executable permissions, and executed detached from the main process. The package masquerades this behavior as telemetry functionality, but no legitimate telemetry occurs. The code uses string concatenation to obfuscate hostnames and API references to evade static detection. There is no official patch or fix currently documented.
The npm package dolyame-ui-deprecatepropshoc version 35.8.1 contains malicious code that executes automatically when required. It downloads and executes a platform-specific binary without any verification, enabling remote code execution on the host system. The malicious payload is disguised under telemetry-related filenames and is triggered even if some components are removed.
The npm package bigops-shared-product-design version 35.9.3 contains malicious code that unconditionally loads a module which downloads and executes a platform-specific native binary from suspicious Cloudflare Workers hosts and fallback DNS-TXT resolver domains. The downloaded payload is saved to temporary directories with masqueraded filenames, given executable permissions, and executed detached from the parent process. This behavior is indicative of a dropper toolkit designed to evade static analysis and persist on the system.
The npm package dolyame-ui-collapseblock version 35.8.1 contains malicious code that automatically fetches and executes an attacker-controlled native binary upon import. The binary is retrieved from obfuscated Cloudflare Workers hosts or via a DNS-TXT covert channel if HTTPS fetches fail. The payload is saved to temporary directories with disguised filenames, given executable permissions, and launched detached from the main process. There is no version pinning or integrity verification, allowing arbitrary code execution unrelated to the package's intended functionality. This behavior is consistent with hostile dropper malware tradecraft.
The npm package dolyame-ui-postcsscustomproperties version 35.8.1 contains malicious code that, upon being required, downloads and executes a platform-specific binary payload. This payload is fetched from Cloudflare Workers hosts or reconstructed from DNS TXT queries, then saved and executed on the host system. The package uses obfuscation techniques such as string splitting and runtime assembly of module names and hostnames to evade static detection. It masquerades as an analytics or telemetry SDK and typosquats the legitimate postcss-custom-properties package.
The npm package dolyame-ui-scrollblock version 35.8.1 contains malicious code that, when imported, downloads and executes attacker-controlled native binaries on the developer's machine. The package uses obfuscated code to reconstruct Cloudflare Workers hostnames and fetch platform-specific payloads, which are saved to temporary directories, given executable permissions, and run detached. A secondary payload delivery method uses DNS TXT record resolution to assemble and execute base64-encoded code. This behavior occurs without any signature verification or pinning, posing a direct risk of remote code execution upon package installation and import.
The npm package ded-pwa-c-mapping version 35.8.7 contains malicious code that, upon requiring the package, executes a bootstrap routine to download and run a native binary payload from dynamically assembled, obfuscated external hosts. The payload is saved under disguised filenames in temporary directories, given executable permissions, and launched detached from the installing process without any integrity verification. The code attempts to evade detection by assembling hostnames at runtime and referencing environment variables to frame the behavior as telemetry. No official patch or remediation guidance is provided.
The npm package dolyame-ui-inputfio version 35.8.1 contains malicious code that executes immediately upon import. It reconstructs obfuscated hostnames to download a binary payload via HTTPS or DNS TXT fallback, writes this payload to temporary disk locations, sets executable permissions, and executes it detached using system shell commands. The package disguises this behavior as an analytics SDK but includes deliberate evasion techniques to avoid static detection.
The npm package ded-pwa-c-boxy-di version 35.2.2 contains malicious code that, when imported, automatically downloads and executes a binary payload from obfuscated remote endpoints without user interaction. The payload is fetched over HTTPS from Cloudflare Workers-hosted domains and a DNS-TXT base64 fallback channel, saved under disguised filenames, given executable permissions, and run detached on the host system. There is no verification of the downloaded payload's integrity or authenticity, increasing the risk of arbitrary code execution.