# MAL-2026-13713: Malicious code in @sqlite-labs/createsql (npm)


- **Type:** Malicious package
- **Package:** `@sqlite-labs/createsql` (npm)
- **Published:** 10 Aug 2026
- **Also known as:** GHSA-qwqp-6xhg-jhhv

## What is MAL-2026-13713?

MAL-2026-13713 is a malicious package in @sqlite-labs/createsql, published on 10 Aug 2026. 

### Official description

The package's main entry (index.js) fetches JavaScript from a hardcoded URL on a Vercel blob storage bucket (https://bdmkaoyijqmqa6bg.public.blob.vercel-storage.com/script.js) and passes the response body directly to eval() as an unconditional top-level side effect. Any consumer that require()s or imports this package downloads and executes attacker-controlled JavaScript in the installer's Node process, with no pinning, no integrity verification, and no relation to the SQL/database purpose implied by the package name. The remote URL is stored in a variable named `gisturl` while actually resolving to a mutable Vercel blob endpoint — a cover-story naming pattern consistent with a dropper rather than legitimate remote configuration.

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

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-13713 is a malicious package: @sqlite-labs/createsql (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-13713/ (Markdown: https://insights.sbomify.com/MAL-2026-13713/index.md)
```

## Sources

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

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