# MAL-2026-5433: Malicious code in @webda-infra/search (npm)


- **Type:** Malicious package
- **Package:** `@webda-infra/search` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-4rmm-f927-v58w

## What is MAL-2026-5433?

MAL-2026-5433 is a malicious package in @webda-infra/search, published on 9 Jun 2026. 

### Official description

@webda-infra/search@99.9.1 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.

## What should I do about MAL-2026-5433?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5433 is a malicious package: @webda-infra/search (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5433/ (Markdown: https://insights.sbomify.com/MAL-2026-5433/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5433

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5433/
Summaries are generated and may contain mistakes; the official description above is the record.