NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-nest-keycloak-connectnpm

Advisory published Updated

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)

MAL-2026-13113
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bpm-foundation-nest-keycloak-connect

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

1 flagged
35.8.6

Indicators of compromise (SHA-256)

6028d40d9f000e522af8bd82686a497d07e5496431bf43fc49161f8b31ac3955

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bpm-foundation-nest-keycloak-connect (version 35.8.6).

  2. 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.

  3. Did it already run?

    If bpm-foundation-nest-keycloak-connect was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bpm-foundation-nest-keycloak-connect on npm has been identified as a malicious package (version 35.8.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015264

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.

Explore

bpm-foundation-nest-keycloak-connect (npm) malicious package — MAL-2026-13113 | O3 Security