# MAL-2026-13441: Malicious code in consumerweb-creditcollection (npm)


- **Type:** Malicious package
- **Package:** `consumerweb-creditcollection` (npm)
- **Published:** 6 Aug 2026
- **Also known as:** GHSA-5h26-cm3q-vvcf

## What is MAL-2026-13441?

MAL-2026-13441 is a malicious package in consumerweb-creditcollection, published on 6 Aug 2026. 

### Official description

consumerweb-creditcollection@99.9.1 is a hollow package whose main index.js exports an empty object. Its sole runtime effect is pulling in a dependency `ltidisafe` pinned to an arbitrary tarball URL on a third-party Google Cloud Storage bucket (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.5.3.tgz`) rather than an npm registry entry. Installing this package causes npm to download and install code from that off-registry URL, which is outside npm registry scanning. The `depenconf` path segment, the internal-sounding package name, and the high version number 99.9.1 are consistent with a dependency-confusion / namespace-squat delivery vector where the lure package's only purpose is to force resolution of attacker-hosted 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-13441?

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

## Sources

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

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