registry / @validate.qa/runner / 1.0.108
@validate.qa/runner@1.0.108
validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.
AI Security Review
scanned 13h ago · by lpm-firewall-aiThe manifest identifies a Playwright test runner and its only lifecycle script builds the package. The routed authentication and dynamic-execution alerts were not supported as attacks by the inspected code.
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
The CLI is invoked to run tests; the prepublishOnly script runs during publishing.
Impact
No malicious impact identified from the reviewed source.
Mechanism
The routed credential-related code validates authentication flows, while the cited chunk is a bundled email address parser. No evidence showed automatic credential exfiltration or remote response execution.
AI rationale
The manifest identifies a Playwright test runner and its only lifecycle script builds the package. The routed authentication and dynamic-execution alerts were not supported as attacks by the inspected code.
Network endpoints1
accounts.google.com
Decision evidence
public snapshotAI called this Clean at 90.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 and exposes a CLI entry point.
- The prepublishOnly hook only runs the build; no install lifecycle hook is declared.
- The routed Google authentication code constructs a request to accounts.google.com and validates authentication-provider sign-in routes, consistent with test-runner authentication handling.
- The routed chunk containing the alleged remote execution is bundled nodemailer address-parser code.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationTelemetryUrlStrings
NoLicenseWildcardDependency
Source & flagged code
15 flaggeddist/discovery-mcp-server.jsView file
15};
L16: var __commonJS = (cb, mod) => function __require() {
L17: try {
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/discovery-mcp-server.jsView on unpkg · L15dist/run-write-guard.jsView file
144ACTION_BATCH_MAX_SIZE = 10;
L145: MOBILE_SCREENSHOT_INTERVAL_MS = typeof process !== "undefined" ? parseInt(process.env?.MOBILE_SCREENSHOT_INTERVAL_MS ?? "500", 10) : 500;
L146: MOBILE_ACTION_BATCH_MAX_SIZE = 5;
...
L320: return false;
L321: if (typeof f.base64 !== "string" || f.base64.length === 0)
L322: return false;
...
L484: "javascript:",
L485: "data:",
L486: "vbscript:",
...
L1168: ``,
L1169: `main().catch((err) => { console.error(err); process.exitCode = 1; });`
L1170: ].join("\n");
Critical
Browser Credential Phishing
Source appears to collect browser login credentials for exfiltration.
dist/run-write-guard.jsView on unpkg · L144Findings
3 Critical12 High7 Medium7 Low
CriticalBrowser Credential Phishingdist/run-write-guard.js
CriticalRemote Response Code Executiondist/chunk-7XB3ETK3.mjs
CriticalPrevious Version Dangerous Deltadist/chunk-7DKIJ2ZX.mjs
HighChild Process
HighShell
HighEval
HighBrowser Session Account Hijackdist/run-write-guard.js
HighCross File Remote Execution Contextdist/chunk-DNE7LB3D.mjs
HighSemantic Analysis Limiteddist/discovery-mcp-server.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritydist/tar-extract-child.js
HighKnown Malware Source Similaritydist/chunk-PUMRAFJS.mjs
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to @validate.qa/runner@1.0.108.
See all versions of @validate.qa/runner for other recorded verdicts.
- Review the evidence and your use of @validate.qa/runner@1.0.108 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.