# MAL-2026-13440: Malicious code in connect-contingency (npm)


- **Type:** Malicious package
- **Package:** `connect-contingency` (npm)
- **Published:** 6 Aug 2026
- **Also known as:** GHSA-3q7q-6272-2v37

## What is MAL-2026-13440?

MAL-2026-13440 is a malicious package in connect-contingency, published on 6 Aug 2026. 

### Official description

connect-contingency@99.9.1 is a hollow package whose index.js is an empty stub. Its package.json declares its sole dependency `ltidisafe` as a direct tarball URL on an anonymous Google Cloud Storage bucket: `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.7.tgz`. On `npm install`, npm downloads that tarball from a non-registry, non-publisher host outside registry integrity/audit coverage and installs it, executing any lifecycle scripts (preinstall/install/postinstall) it declares. The package name, an inflated 99.9.x version characteristic of dependency-confusion staging, the empty main, and the `/depenconf/` URL path together indicate a dependency-confusion lure whose only effect on install is to pull attacker-controlled code into the installer's environment.

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

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-13440 is a malicious package: connect-contingency (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-13440/ (Markdown: https://insights.sbomify.com/MAL-2026-13440/index.md)
```

## Sources

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

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