statist-browser-typed-client-rubliq.platform.keycloaknpm
Advisory published Updated
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.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for statist-browser-typed-client-rubliq.platform.keycloak (version 20.2.5).
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 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
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.