MAL-2026-12162 Malicious code in bigops-customer-processing-client (npm)
Malicious package
Published
MAL-2026-12162 is a malicious package: bigops-customer-processing-client (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-12162/ (Markdown: https://insights.sbomify.com/MAL-2026-12162/index.md)
- Package
- bigops-customer-processing-client
- Registry
- npm
What is MAL-2026-12162?
MAL-2026-12162 is a malicious package in bigops-customer-processing-client, published on 5 Aug 2026.
Official description
On require() of this package, index.js loads support.js which unconditionally invokes setup(). setup() assembles C2 hostnames via.join('') from fragmented substrings, resolving to *.workers.dev endpoints (oob-worker.cf100-416.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev) with a DNS-TXT fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. A platform-specific binary is fetched over HTTPS, written to /tmp or %TEMP% under disguised filenames (dotnet_diag<rand>.exe,.cache_<rand>), chmod 0755, and detach-spawned via cmd /c start /b or /bin/sh -c. No hash or signature verification is performed despite a comment claiming a SHA-256 check. Hostname fragmentation, cover-story comments, and disguised drop paths indicate deliberate evasion.
What should I do about MAL-2026-12162?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.