# MAL-2026-10577: Malicious code in @sqlite-clone/nodesql (npm)


- **Type:** Malicious package
- **Package:** `@sqlite-clone/nodesql` (npm)
- **Published:** 14 Jul 2026
- **Also known as:** GHSA-x8m3-m829-mhc4

## What is MAL-2026-10577?

MAL-2026-10577 is a malicious package in @sqlite-clone/nodesql, published on 14 Jul 2026. 

### Official description

The package is published as @sqlite-clone/nodesql but its shipped index.js is a verbatim copy of the well-known feross/buffer polyfill with a single injected top-level statement: `var ins = import('@sqlite-panel/createsql');`. This dynamic import fires whenever a consumer requires or imports the package, transitively loading and executing whatever code the sibling scoped package @sqlite-panel/createsql ships. The package name, keywords ('node','sql'), README (titled 'bare-stream' and instructing users to `npm i @sql-access/nods`), and actual code body (buffer polyfill) do not agree with each other, and the declared dependency lives under a third, unrelated scope — a lure/cover-story shape rather than a legitimate library. The buffer-polyfill body serves as camouflage: the tarball has no direct network I/O of its own; the entire supply-chain effect is delivered through the transitively pulled attacker-controlled dependency.

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

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

## Sources

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

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