delivery-ci-update-gitlabnpm

On require(), index.js loads adapter.js which fetches an unsigned, unhashed platform-specific executable from hardcoded Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev), writes it to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and detached-spawns it via child_process.spawn on /bin/sh or cmd. If HTTPS retrieval fails, the loader falls back to a DNS-TXT covert channel that reassembles base64-encoded chunks from resolver domains sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, reconstructs the binary, and executes it. Hostnames are assembled from split string fragments (e.g. ['oob-worker.','cf100-41','6.workers.dev'].join('')), a.analytics_state stamp file is written, and environment variables named DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK frame the behavior as telemetry despite the payload being an executable binary. Package metadata is placeholder (empty dependencies, no repository/author) and the name impersonates an internal CI/GitLab tool.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.