statist-browser-typed-client-rubliq.platform.keycloaknpm
statist-browser-typed-client-rubliq.platform.keycloak is a confirmed malicious npm package (MAL-2026-12451) that steals credentials and exfiltrates sensitive data (malicious version 20.2.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in statist-browser-typed-client-rubliq.platform.keycloak (npm)
What this malware does
The package presents itself as a Keycloak typed client but on require() executes a binary dropper. index.js loads adapter.js, which reconstructs destination hostnames from split string fragments joined via.join('') to hide them from static analysis, selects a platform-specific URL, and downloads a binary over HTTPS from Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev). The downloaded bytes are written to /tmp or the Windows Temp directory under disguised names (.analytics_state, dotnet_diag.exe,.cache_), chmodded to 0755, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start. A DNS-TXT covert-channel fallback under subdomains of dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site) reassembles a base64-encoded binary from TXT record chunks when HTTPS fetch fails, feeding the same write+chmod+spawn chain. The child_process module name is constructed as require('child_' + 'process') and chmodSync is accessed as fs['chmod'+'Sync'] to further evade pattern matching. Environment variables DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK are checked to give the behavior a telemetry cover story. lib/telemetry.js contains a parallel dropper implementation with the same primitives, wrapped in 'Analytics SDK' comments. The package name resembles a legitimate Keycloak client but the shipped code performs installer-side arbitrary code execution rather than any Keycloak functionality.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for statist-browser-typed-client-rubliq.platform.keycloak (version 20.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging statist-browser-typed-client-rubliq.platform.keycloak across your stack and pipelines.
If you installed it — respond
statist-browser-typed-client-rubliq.platform.keycloak is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If statist-browser-typed-client-rubliq.platform.keycloak 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 statist-browser-typed-client-rubliq.platform.keycloak 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 statist-browser-typed-client-rubliq.platform.keycloak-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.