# MAL-2026-4440: Malicious code in @serviceshub/x-web-core (npm)


- **Type:** Malicious package
- **Package:** `@serviceshub/x-web-core` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-xjvj-r6v9-q99q

## What is MAL-2026-4440?

MAL-2026-4440 is a malicious package in @serviceshub/x-web-core, published on 20 May 2026. 

### Official description

Package ships a trivial index.js (`module.exports = {};`) and exists solely to pull a direct-URL tarball dependency at install time. package.json line 9 declares `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.9.tgz"` — an unpinned (no integrity hash, mutable bucket object) tarball hosted outside the npm registry, bypassing registry-side audit. The bucket path literally contains the string `depenconf` (dependency-confusion). On `npm install`, npm fetches the GCS tarball and runs any lifecycle scripts inside it on the installer's machine; the author can swap the tarball bytes at any time. Corroborating signals: version is squatted at `99.9.1` for a brand-new scope, `description` and `author` fields are empty, and the main module has no functionality matching the package's `x-web-core` name. The package itself is a lure whose only effect on install is to pull attacker-controlled, non-registry, mutable code into the installer's dependency tree.

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

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-4440 is a malicious package: @serviceshub/x-web-core (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-4440/ (Markdown: https://insights.sbomify.com/MAL-2026-4440/index.md)
```

## Sources

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

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