q-koa@13.8.69
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source exposes request-supplied JavaScript evaluation through the model read API, creating a server-side code execution risk whose effective access controls depend on configuration. I found no install lifecycle behavior or separate malicious payload chain, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The manifest points to index.js and declares no install or import lifecycle hook.
- A model read request takes include from the request body, and the framework wraps it in eval and invokes the resulting function on the application object.
- The model read path has a configuration-dependent exclusion check, while the middleware permits some requests without token verification.
- The startup subscriber listens for cache clear and only clears the selected cache entry.
- The inspected startup subscription performs a routine cache clear; no account-changing behavior was found there.
- The flagged service integrations use their corresponding official service endpoints.
Source & flagged code
17 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
core/file/plugins/common/controller.jsView on unpkgPackage contains a possible secret pattern.
core/file/plugins/common/controller.jsView on unpkg · L184Package source references weak cryptographic algorithms.
Findings
Affected versions and remediation
This report applies to q-koa@13.8.69.
See all versions of q-koa for other recorded verdicts.
- Review the evidence and your use of q-koa@13.8.69 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.