MAL-2026-13494 Malicious code in bigops-telephony-mock (npm)
Malicious package
Published
MAL-2026-13494 is a malicious package: bigops-telephony-mock (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-13494/ (Markdown: https://insights.sbomify.com/MAL-2026-13494/index.md)
- Package
- bigops-telephony-mock
- Registry
- npm
What is MAL-2026-13494?
MAL-2026-13494 is a malicious package in bigops-telephony-mock, published on 7 Aug 2026.
Official description
Requiring the package (index.js ->./setup) triggers setup.js, which reconstructs destination hostnames from split string fragments (e.g. oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, downloads a platform-specific binary via https.get, writes it to a disguised path under /tmp or %TEMP% (names such as analytics_state, dotnet_diag_.exe,.cache_), fs.chmodSync's it to 0755, and cp.spawn's it detached via /bin/sh -c '<file> &' or cmd.exe /c start /b. No version pin, no hash or signature verification, and destinations are assembled at runtime to defeat static inspection; child_process itself is required as "child_" + "process" in lib/telemetry.js. A second copy of the same download->base64-decode->chmod 755->spawn /bin/sh loader is bundled under lib/telemetry.js (approximately 81KB) framed as a telemetry SDK. The behavior fires on any require()/import of the package, gated only by an opt-out env var and a TTL marker file, so a normal npm install followed by loading the module causes attacker-controlled code to execute on the installer's machine.
What should I do about MAL-2026-13494?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.