registry / @validate.qa/runner / 1.0.107
@validate.qa/runner@1.0.107
validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package identifies itself as a local Playwright runner, and the inspected credential flow uses a configured broker and app-host restrictions. The dynamic execution hint is consistent with validating generated test code; the inspected evidence does not establish credential theft or concealed remote code execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
User-run test runner activity or an explicit credential-filling tool call.
Impact
The inspected behavior supports running tests and entering test credentials into the app under test; no unrelated collection or concealed remote execution was established.
Mechanism
The runner executes test workflows and sends credential references to a session-configured broker; the fill policy checks the target page against configured app hosts.
AI rationale
The package identifies itself as a local Playwright runner, and the inspected credential flow uses a configured broker and app-host restrictions. The dynamic execution hint is consistent with validating generated test code; the inspected evidence does not establish credential theft or concealed remote code execution.
Network endpoints2
User-configured VQA_CREDENTIAL_BROKER_URL/credentialsaccounts.google.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a local Playwright test runner connected to validate.qa.
- Credential fields use a secret key reference instead of placing the credential value in the field record.
- Credential filling requires a broker URL and token from session environment variables; the broker request uses the `fill` operation.
- Credential filling checks that the page is a web page and restricts it to configured app hosts, with a specific Google sign-in exception.
- The dynamic `new Function` site shown validates generated test code after stripping imports and TypeScript syntax.
Evidence against
- The package includes process execution, network access, and dynamic code construction, but the inspected code ties these to test-runner and credential-filling features.
- The scanner’s browser-credential and remote-execution alerts are not confirmed as credential theft or concealed remote code execution in the inspected paths.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
12 flaggeddist/chunk-EAFAY4YD.mjsView file
46var harness_init_script_js_1 = require_harness_init_script();
L47: exports.IS_CLOUD = (0, shared_1.parseBoolFlag)(process.env.RUNNER_CLOUD);
L48: var BROWSER_ENV_ALLOW_NAMES = /* @__PURE__ */ new Set([
...
L141: ]);
L142: var BROWSER_ENV_SECRET_NAME = new RegExp("(?:^|_)(?:TOKEN|SECRET|PASSWORD|PASSWD|PASSCODE|PASS|PAT|DSN|CREDENTIALS?|API_?KEY|PRIVATE_?KEY|ACCESS_?KEY)(?:_|$)|_KEY$|(?:^|_)AUTH$|^AU...
L143: function operatorBrowserEnvAllow(source) {
...
L645: exports.collectDescendants = collectDescendants;
L646: var node_child_process_1 = __require("child_process");
L647: var node_util_1 = __require("util");
...
L656: try {
L657: const { stdout } = await execFileAsync("ps", ["-A", "-o", "pid=,ppid=,command="], {
L658: maxBuffer: proc_table_js_1.PS_MAX_BUFFER,
Critical
Browser Credential Phishing
Source appears to collect browser login credentials for exfiltration.
dist/chunk-EAFAY4YD.mjsView on unpkg · L4646Cross-file remote execution chain: dist/chunk-EAFAY4YD.mjs spawns dist/chunk-BZAH6ONA.mjs; helper contains network access plus dynamic code execution.
L46: var harness_init_script_js_1 = require_harness_init_script();
L47: exports.IS_CLOUD = (0, shared_1.parseBoolFlag)(process.env.RUNNER_CLOUD);
L48: var BROWSER_ENV_ALLOW_NAMES = /* @__PURE__ */ new Set([
...
L141: ]);
L142: var BROWSER_ENV_SECRET_NAME = new RegExp("(?:^|_)(?:TOKEN|SECRET|PASSWORD|PASSWD|PASSCODE|PASS|PAT|DSN|CREDENTIALS?|API_?KEY|PRIVATE_?KEY|ACCESS_?KEY)(?:_|$)|_KEY$|(?:^|_)AUTH$|^AU...
L143: function operatorBrowserEnvAllow(source) {
...
L645: exports.collectDescendants = collectDescendants;
L646: var node_child_process_1 = __require("child_process");
L647: var node_util_1 = __require("util");
...
L656: try {
L657: cons
Findings
3 Critical10 High7 Medium7 Low
CriticalBrowser Credential Phishingdist/chunk-EAFAY4YD.mjs
CriticalRemote Response Code Executiondist/chunk-BZAH6ONA.mjs
CriticalPrevious Version Dangerous Deltadist/chunk-H5GLEPYC.mjs
HighChild Process
HighShell
HighEval
HighCross File Remote Execution Contextdist/chunk-EAFAY4YD.mjs
HighKnown Malware Source Similaritydist/tar-extract-child.js
HighKnown Malware Source Similaritydist/chunk-PUMRAFJS.mjs
HighKnown Malware Source Similaritydist/chunk-BZAH6ONA.mjs
HighKnown Malware Source Similaritydist/chunk-GABQIU5P.mjs
HighKnown Malware Source Similaritydist/chunk-SQXBAGIW.mjs
Affected versions and remediation
This report applies to @validate.qa/runner@1.0.107.
See all versions of @validate.qa/runner for other recorded verdicts.
- Review the evidence and your use of @validate.qa/runner@1.0.107 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.