bigops-storio-schematicsnpm
bigops-storio-schematics is a confirmed malicious npm package (MAL-2026-13255) that executes malicious code on install (malicious version 35.3.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-storio-schematics (npm)
What this malware does
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-storio-schematics (version 35.3.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-storio-schematics across your stack and pipelines.
If you installed it — respond
Remove bigops-storio-schematics from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bigops-storio-schematics was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bigops-storio-schematics before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bigops-storio-schematics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.