bigops-storio (npm) · Malicious Code

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (072daea48b555582ea01125b1a71fff5907e73bc890ec56f7b012ac38230b69e) On require() of bigops-storio, _support.js selects a platform-specific endpoint and fetches an opaque binary over HTTPS from one of four string-split *.workers.dev hosts (oob-worker.cf100-416.workers.dev, cf101-adf, cf99-9b3, cf103-070 under workers.dev), assembled at runtime via array.join("") to hide the destinations from static inspection. The fetched bytes are written to /tmp or %TEMP% under a hidden random filename (dot-prefixed / dotnet_diag-style cover names), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe /c start /b with stdio ignored. A DNS-TXT fallback (txtFetch/dns.resolveTxt against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru — also assembled from string fragments) reassembles N base64-encoded TXT chunks into the same executable payload when HTTPS delivery fails. There is no version pinning, no hash or signature verification, and the fetched executable is unrelated to the package's stated storio abstraction purpose. The dropper runs automatically at library load time via index.js's try{require('./_support')}. ## Source: ghsa-malware (cd9ebb4bf8d8e6554d93f8343675d991c677dea6469481d1689813b405dca59c) 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/v/35.8.7 (opens in a new tab)
• github.com/advisories/GHSA-g548-9c3x-q2r5 (opens in a new tab)