Which versions of @sqlite-frame/nodesql are malicious?

The following npm versions of @sqlite-frame/nodesql are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate @sqlite-frame/nodesql if I installed it?

Remove @sqlite-frame/nodesql from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @sqlite-frame/nodesql — how do I know if it already compromised me?

If @sqlite-frame/nodesql was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @sqlite-frame/nodesql part of a known attack campaign?

Yes — @sqlite-frame/nodesql is associated with the IN-MAL-2026-010593, IN-MAL-2026-010592, GHSA-r9rm-52xp-prf4 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @sqlite-frame/nodesql across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sqlite-frame/nodesql (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sqlite-frame/nodesql across your stack and pipelines.

Malicious package

@sqlite-frame/nodesqlnpm

@sqlite-frame/nodesql is a confirmed malicious npm package (MAL-2026-10627) that executes malicious code on install (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sqlite-frame/nodesql (npm)

MAL-2026-10627

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @sqlite-frame/nodesql

What this malware does

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.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

0b24506932cbd3f2258f2448b83918ba2acee09cd896467780f8b1dc18b9eb42

bd05dbbbc74741e39f6e07b882d8c4ee1581fcd1ff714438cd4c764b5c28fbdf

05b26ce7b19d0fdc8b846970970de2af18dabe7705165910a9b538758b883fd3

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sqlite-frame/nodesql (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sqlite-frame/nodesql across your stack and pipelines.
If you installed it — respond
Remove @sqlite-frame/nodesql from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @sqlite-frame/nodesql was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @sqlite-frame/nodesql before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @sqlite-frame/nodesql on npm has been identified as a malicious package (versions 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010593IN-MAL-2026-010592GHSA-r9rm-52xp-prf4

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sqlite-frame/nodesql-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database