MAL-2026-13220 Malicious code in bigops-jsonpath-mapper (npm)
Malicious package
Published
MAL-2026-13220 is a malicious package: bigops-jsonpath-mapper (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-13220/ (Markdown: https://insights.sbomify.com/MAL-2026-13220/index.md)
- Package
- bigops-jsonpath-mapper
- Registry
- npm
What is MAL-2026-13220?
MAL-2026-13220 is a malicious package in bigops-jsonpath-mapper, published on 5 Aug 2026.
Official description
On require of bigops-jsonpath-mapper, index.js loads bridge.js which assembles hostnames from string-array joins to hide the destinations (oob-worker.cf99-9b3.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev, with DNS-TXT chunked-base64 fallback to *.dl.wel1.ru), fetches a platform-specific native binary over HTTPS, writes it to /tmp or %TEMP% under disguised names such as.cache<hex> and dotnet_diag_<hex>.exe, chmods 0755 on Unix, and spawns it detached and unref'd via spawn("/bin/sh",…) or spawn("cmd",…). A /tmp/.analytics_state TTL file suppresses re-execution across imports. Comments frame the behavior as telemetry/session tracking, but the shipped code is a fetch-and-execute dropper of opaque bytes from author-controlled non-publisher infrastructure that runs at module load time.
What should I do about MAL-2026-13220?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.