q-koa@13.8.54
AI Security Review
scanned 27d ago · by lpm-firewall-aiq-koa is a Koa admin framework with no install lifecycle, but its find handler executes request-body include and relate strings through vm.runInNewContext while the default JWT check allows any URL containing find. That is a concrete unauthenticated code-execution and SQL-injection flaw in the running server, not a hidden supply-chain payload.
Decision evidence
public snapshot- Model find handlers take include and relate from the HTTP body, wrap them as eval(...), and run them with vm.runInNewContext, then call the result with the live app object.
- The default JWT whitelist contains the substring find, and a failed token still continues when the URL includes any whitelist entry, the method is GET, the URL contains a dot, or the client is treated as local.
- The system plugin interpolates the request model name into a raw INFORMATION_SCHEMA SQL string.
- package.json has no preinstall, install, or postinstall hook; its scripts are ordinary debug, pm2 serve, and shell PATH commands.
- No child_process, install-time execution, credential harvest, or hidden outbound recipient was found.
- The eval path is the framework's Sequelize include builder, not a separate payload dropper.
- Outbound HTTP usage is in payment, map, WeChat, and Douyin service modules.
Source & flagged code
8 flagged · loading sourcePackage contains a possible secret pattern.
core/file/plugins/common/controller.jsView on unpkg · L184Package source references weak cryptographic algorithms.
core/file/plugins/common/controller.jsView on unpkg · L15Findings
Affected versions and remediation
This report applies to q-koa@13.8.54.
See all versions of q-koa for other recorded verdicts.
- Review the evidence and your use of q-koa@13.8.54 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.