@ultrst-armada/kloks@1.24.11
Kloks — Public Backend, State-Graph, Audio/MIDI & Service Package Library built on KrnlTS (@kloks/*)
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe backend's Cloudflare error handler forwards the user's token and account ID to the SRKL service, whose default host is controlled by the package publisher. This is credential exfiltration even though it occurs only after the normal Cloudflare request fails.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A caller invokes fetchCloudflareData with a Cloudflare token, and the normal provider lookup throws an error.
Impact
The SRKL service receives the user's Cloudflare credential and could use it to access the associated account.
Mechanism
The catch handler places the token and account ID in the query string of a request to the SRKL resources endpoint; its default host is srkl-engine.vercel.app.
Attack narrative
When Cloudflare data retrieval fails, the exported backend function sends the supplied Cloudflare token and account ID to an SRKL endpoint. If no deployment URL is resolved, the endpoint defaults to srkl-engine.vercel.app. This discloses a third-party service credential to the package vendor during error handling without an explicit consent step.
AI rationale
The backend's Cloudflare error handler forwards the user's token and account ID to the SRKL service, whose default host is controlled by the package publisher. This is credential exfiltration even though it occurs only after the normal Cloudflare request fails.
Evidence
packages/backend/dist/index.jspackages/backend/dist/chunk-HF5SGQ5V.js
Network endpoints2
srkl-engine.vercel.appapi.cloudflare.com
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- On Cloudflare request failure, fetchCloudflareData sends the Cloudflare token and account ID to the SRKL resources endpoint.
- The endpoint falls back to the hard-coded host srkl-engine.vercel.app.
- fetchCloudflareData accepts tokens from its payload or credentials object and is exported by the backend.
Evidence against
- The package implements provider integrations that normally send credentials to their corresponding official APIs.
- The SRKL request is in an error fallback, rather than the normal successful Cloudflare response path.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggedpackages/state-graph/dist/transformers.node-HWHOAE4H.jsView file
33"use strict";
L34: var fs6 = __require("fs");
L35: var LDD_PATH = "/usr/bin/ldd";
Medium
Dynamic Require
Package source references dynamic require/import behavior.
packages/state-graph/dist/transformers.node-HWHOAE4H.jsView on unpkg · L3318054${m}
L18055: }`, n = new Function(Object.keys(h), m)(...Object.values(h)), m = `methodCaller<(${u.map((y) => y.name)}) => ${o.name}>`, Fi(Object.defineProperty(n, "name", { value: m }));
L18056: }
Low
Eval
Package source references a known benign dynamic code generation pattern.
packages/state-graph/dist/transformers.node-HWHOAE4H.jsView on unpkg · L18054packages/services/dist/index.jsView file
Findings
1 Critical2 High4 Medium7 Low
CriticalHardcoded Runtime Data Exfiltrationpackages/services/dist/index.js
HighSemantic Analysis Limitedpackages/backend/dist/chunk-RCCQ7IRM.js
HighPrevious Version Dangerous Deltapackages/backend/dist/chunk-3VWBZEMG.js
MediumDynamic Requirepackages/state-graph/dist/transformers.node-HWHOAE4H.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvalpackages/state-graph/dist/transformers.node-HWHOAE4H.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Low
Affected versions and remediation
This report applies to @ultrst-armada/kloks@1.24.11.
See all versions of @ultrst-armada/kloks for other recorded verdicts.
- Avoid installing @ultrst-armada/kloks@1.24.11. 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.