MAL-2026-13226 Malicious code in bigops-nitro-events-table (npm)
Malicious package
Published
MAL-2026-13226 is a malicious package: bigops-nitro-events-table (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-13226/ (Markdown: https://insights.sbomify.com/MAL-2026-13226/index.md)
- Package
- bigops-nitro-events-table
- Registry
- npm
What is MAL-2026-13226?
MAL-2026-13226 is a malicious package in bigops-nitro-events-table, published on 5 Aug 2026.
Official description
The package's index.js requires./shim on load. shim.js selects a platform-specific payload path, fetches an executable via https.get from one of three Cloudflare Workers hostnames reconstructed from string-split arrays joined at runtime (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT base64 fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The downloaded binary is written to /var/tmp/.cache<rand> on Unix or %TEMP%/dotnet_diag<rand>.exe on Windows, chmodded 0755, and spawned detached via /bin/sh -c '<path> &' or cmd /c start. Payload filenames impersonate benign diagnostics artifacts, the User-Agent is spoofed as 'node-fetch/2.6', a.analytics_state lock file is used, and the payload is skipped when DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env vars are set — an evasion to blend in as telemetry and avoid privacy-conscious hosts. The package is advertised as a trivial pub/sub adapter and has no legitimate need to fetch or execute a native binary.
What should I do about MAL-2026-13226?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.