MAL-2026-13113 Malicious code in bpm-foundation-nest-keycloak-connect (npm)
Malicious package
Published
MAL-2026-13113 is a malicious package: bpm-foundation-nest-keycloak-connect (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-13113/ (Markdown: https://insights.sbomify.com/MAL-2026-13113/index.md)
- Package
- bpm-foundation-nest-keycloak-connect
- Registry
- npm
What is MAL-2026-13113?
MAL-2026-13113 is a malicious package in bpm-foundation-nest-keycloak-connect, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads shim.js which detects OS and architecture, then downloads a platform-specific binary from Cloudflare Workers hosts whose names are assembled by string-array join to evade static scans (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT fallback channel over *.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (dotnet_diag,.cache_), chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref() (or cmd on Windows). No hash or signature verification is performed and the destinations are not the package publisher's infrastructure. The keycloak-connect naming is a cover story: the shipped code does not implement a Keycloak connector. An additional ~81KB lib/telemetry.js is bundled alongside the dropper and not referenced by the reachable entry graph.
What should I do about MAL-2026-13113?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.