@webda-infra/searchnpm
Advisory published Updated
@webda-infra/search is a confirmed malicious npm package (MAL-2026-5433) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @webda-infra/search (npm)
What this malware does
@webda-infra/[email protected] is a near-empty placeholder (index.js is empty, module.exports = {}) whose package.json declares a single dependency, ltidisafe, resolved via a direct URL to a Google Cloud Storage bucket: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.8.4.tgz. The path segment depenconf, the burner-style version 99.9.1 chosen to outrank any legitimate internal @webda-infra/* package, and the absence of an integrity hash or version pin combine into a dependency-confusion / namespace-squat shape: any npm install that resolves this public package will fetch and install whatever bytes are hosted at that GCS URL, including any preinstall/install/postinstall lifecycle scripts in the resulting tarball. The GCS bucket is unrelated to any verified webda / webda-infra publisher and the URL is mutable — the operator can swap the served bytes at any time. The entire reason to install this package is to pull and execute arbitrary off-registry code on the installer's machine.
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
Malicious packageFind it
Search your lockfiles and build artifacts for @webda-infra/search (version 99.9.1).
If you installed it — respond
Remove @webda-infra/search 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.
Did it already run?
If @webda-infra/search 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
- ReversingLabs · finder
Detect & block this
O3 blocks @webda-infra/search-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.