webservices.rest-utilsnpm
Malicious code in webservices.rest-utils (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares both preinstall and postinstall hooks that execute index.js, which exfiltrates installer data to a base64-encoded Cloudflare Worker destination (openmrs-sol-dev-v2.lapxa354.workers.dev). The payload includes hostname, username, network interfaces, /etc/resolv.conf,.git/HEAD, ~40 CI/CD environment variables (GITHUB_, GITLAB_, AWS_, CIRCLE_, BUILDKITE_, VERCEL_, etc.), recursively walked package.json metadata,.npmrc registry/scope hints, and presence indicators for ~/.ssh, ~/.aws/credentials, ~/.kube/config, ~/.docker, ~/.npmrc, ~/.gitconfig, shell histories. When cloud env-var probes match, the script contacts the cloud metadata IP (encoded as decimal 2852039166 == 169.254.169.254) to harvest live AWS IMDSv2 IAM tokens, GCP service-account access tokens, and Azure managed-identity tokens — first 40 characters of each are appended to the exfil. It additionally performs DNS reconnaissance against ~25 internal hostnames (kubernetes.default.svc.cluster.local, vault.internal, consul.service.consul, gitlab.local, jenkins.local, ec2.internal, rancher.internal, etc.) for lateral-movement targeting. package.json declares 11 bin aliases — webpack, vite, tsc, eslint, jest, gulp, next, turbo, prettier, tsnode — all pointing at the same malicious index.js, so every subsequent invocation of those common dev commands re-triggers the exfiltrator while forwarding to the real tool to mask the hijack. Obfuscation (base64 destination, decimal-encoded metadata IP, MalekAbuLialaResearch/1.0 cover User-Agent, [Webpack-Debug-MAB-v1] log label) confirms intent.
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for webservices.rest-utils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging webservices.rest-utils across your stack and pipelines.
If you installed it — respond
webservices.rest-utils 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 webservices.rest-utils 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 webservices.rest-utils 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 webservices.rest-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.