# MAL-2026-10627: Malicious code in @sqlite-frame/nodesql (npm)


- **Type:** Malicious package
- **Package:** `@sqlite-frame/nodesql` (npm)
- **Published:** 15 Jul 2026
- **Also known as:** GHSA-r9rm-52xp-prf4

## What is MAL-2026-10627?

MAL-2026-10627 is a malicious package in @sqlite-frame/nodesql, published on 15 Jul 2026. 

### Official description

index.js is a near-verbatim copy of the upstream feross/buffer library with a single injected top-level statement `var ins = import('@sqlite-frame/createsql');` placed immediately after 'use strict'. On any `require('@sqlite-frame/nodesql')`, Node dynamically imports the sibling scoped package @sqlite-frame/createsql (declared as a runtime dependency), causing that package's code to execute in the consumer's process without user awareness. The README compounds the deception: it presents the package as `bare-stream` and instructs `npm i @sql-access/nods`, while the tarball is actually published as @sqlite-frame/nodesql and ships a Buffer clone rather than a streaming library. Author metadata and the repository `guilderguzman/sql-link` do not match the advertised identity. This is a lure/wrapper whose only added behavior over the upstream library it copies is to smuggle a sibling package into the dependency graph and auto-load it on import.

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

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

## Sources

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

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