Which versions of @sqlite-panel/createsql are malicious?

The following npm versions of @sqlite-panel/createsql are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @sqlite-panel/createsql if I installed it?

Remove @sqlite-panel/createsql 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-panel/createsql — how do I know if it already compromised me?

If @sqlite-panel/createsql 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-panel/createsql part of a known attack campaign?

Yes — @sqlite-panel/createsql is associated with the IN-MAL-2026-010313, GHSA-mq68-3vc3-ch3q 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-panel/createsql 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-panel/createsql (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sqlite-panel/createsql across your stack and pipelines.

Malicious package

@sqlite-panel/createsqlnpm

@sqlite-panel/createsql is a confirmed malicious npm package (MAL-2026-10490) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sqlite-panel/createsql (npm)

MAL-2026-10490

Immediate action

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

npm uninstall @sqlite-panel/createsql

What this malware does

The package's main entry point (index.js) fetches a hardcoded GitHub Gist owned by 'getchainverse' via api.github.com and passes the returned file content directly to eval() at load time. Any consumer that require()s or imports @sqlite-panel/createsql executes whatever JavaScript the gist owner has published, with full Node.js process privileges on the installer's machine. The gist source is mutable and controlled by a third party, with no pinning, hash, or signature verification. The package ships no SQL functionality despite its name; the entire module is the remote-eval dropper. Package metadata (author, description) is empty, and the name appears designed to attract developers searching for SQLite tooling.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bb20d0c9e601940f84c676cd74d174e06a740b6bcb90c12d38cdcecc6ca68696

2ba2859eab361c07b35a901cb4b2811a2518c6c6b5ba1c75efdf9b4f24787ba0

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-panel/createsql (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sqlite-panel/createsql across your stack and pipelines.
If you installed it — respond
Remove @sqlite-panel/createsql 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-panel/createsql 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-panel/createsql 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-panel/createsql on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010313GHSA-mq68-3vc3-ch3q

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sqlite-panel/createsql-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