bpm-foundation-nest-keycloak-connectnpm
bpm-foundation-nest-keycloak-connect is a confirmed malicious npm package (MAL-2026-13113) that executes malicious code on install (malicious version 35.8.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-nest-keycloak-connect (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-nest-keycloak-connect (version 35.8.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-nest-keycloak-connect across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-nest-keycloak-connect from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bpm-foundation-nest-keycloak-connect was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bpm-foundation-nest-keycloak-connect before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bpm-foundation-nest-keycloak-connect-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.