webservices.restnpm
Malicious code in webservices.rest (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package name webservices.rest impersonates the OpenMRS REST API naming convention and is published at version 99.1.0 — the canonical dependency-confusion version-bump pattern designed to outrank an internal/private package of the same name in mixed registry resolution. The package's only functional behavior is to load a separate, caret-pinned dependency webservices.rest-utils@^1.0.5: package.json declares "postinstall": "node index.js", and index.js line 2 calls require('webservices.rest-utils') wrapped in an empty try/catch that suppresses any errors. This means npm install webservices.rest silently fetches and executes whatever code webservices.rest-utils contains, both at install (via postinstall) and at import. Additional integrity-of-publication red flags: README claims an 'OpenMRS Community Contributor' affiliation, but the LICENSE file copyright is held by 'dov-nods-autho' and the declared license disagrees between package.json (Apache-2.0) and the LICENSE file (MIT). The package itself contains no other functionality — it is a thin loader stub whose sole supply-chain effect is to drag the caret-pinned utility package into the installer's dependency tree and execute it.
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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for webservices.rest (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 across your stack and pipelines.
If you installed it — respond
webservices.rest is a typosquat — you almost certainly intended a legitimately-named package. Remove webservices.rest, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If webservices.rest 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 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-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.