bigops-storio-schematics (npm) · Malicious Code

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (85f76938cd11389b3bd414591165194a80fb7188a92630a675a68c5cdb61202b) index.js unconditionally requires _runtime.js, whose top-level start() function selects a platform-specific asset path, fetches an opaque binary from string-array-obfuscated hostnames reconstructed at runtime (oob-worker.cf1-03-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to a hidden file under /tmp or %TEMP% with a random suffix (e.g..cache_<hex> or dotnet_diag_<hex>.exe), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd /c start /b. A fallback covert channel resolves c.<domain> TXT records for a chunk count, then fetches <i>.<domain> TXT records from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru and base64-decodes the concatenation into the executable payload, bypassing HTTP egress filtering. No hash or signature verification is performed and the destination is not the publisher. A sibling file lib/telemetry.js under an 'analytics-sdk' cover story ships the same download→base64-decode→chmod 0755→sh -c file & chain as a staged alternate payload. Requiring or installing this package causes attacker-controlled native code to run on the installer's machine. ## Source: ghsa-malware (a5faa7e2f12c9eabdb7879bf9d4b2aaf2310f04df1c66c3de3dadaad22ad7358) 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.

• npmjs.com/package/bigops-storio-schematics/v/35.3.6 (opens in a new tab)
• github.com/advisories/GHSA-fv5m-hw6g-r9h3 (opens in a new tab)