registry / @wdio/browserstack-service / 9.39.2
@wdio/browserstack-service@9.39.2
WebdriverIO service for better Browserstack integration
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected entrypoints implement BrowserStack testing, diagnostics, and CLI management without an installation attack chain. No concrete credential diversion, broad agent-control mutation, or malicious persistence was established.
Static reason
One or more suspicious static signals were detected.
Trigger
Configured WebdriverIO test runs and argument-controlled cleanup activate these operations.
Impact
Testing operations create logs and caches and transmit diagnostics to BrowserStack; no concrete malicious behavior was established.
Mechanism
The service authenticates BrowserStack requests, uploads diagnostic archives, and manages its testing CLI.
AI rationale
The inspected entrypoints implement BrowserStack testing, diagnostics, and CLI management without an installation attack chain. No concrete credential diversion, broad agent-control mutation, or malicious persistence was established.
Evidence
logs/bstack-wdio-service.loglog/sdk-cli-debug.log
Network endpoints3
api.browserstack.comcollector-observability.browserstack.comupload-observability.browserstack.com
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle hooks or runtime dependency on itself.
- build/cleanup.js requires upload arguments and BrowserStack credentials before uploading service logs.
- build/index.js sends log archives to BrowserStack observability endpoints.
- Captured test configuration passes through sensitive-content redaction.
- Regional endpoint updates come from the BrowserStack CLI session response.
- Subprocess execution starts the testing SDK CLI, and archive extraction rejects paths outside its directory.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedbuild/cleanup.jsView file
380import util, { promisify } from "node:util";
L381: import { exec } from "node:child_process";
L382: import { Readable } from "node:stream";
High
build/index.jsView file
19L20: // package.json
L21: var package_default;
...
L28: author: "BrowserStack <support@browserstack.com>",
L29: homepage: "https://github.com/browserstack/wdio-browserstack-service",
L30: license: "MIT",
...
L354: if (!res.ok) {
L355: throw new ResponseError(`Error response from server ${res.status}: ${await res.text()}`, res);
L356: }
...
L359: function _fetch(input, init) {
L360: const proxyUrl = process.env.HTTP_PROXY || process.env.HTTPS_PROXY;
L361: if (proxyUrl) {
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
build/index.jsView on unpkg · L19Findings
4 High3 Medium5 Low
HighChild Processbuild/cleanup.js
HighShell
HighCommand Output Exfiltrationbuild/index.js
HighCross File Remote Execution Contextbuild/index.js
MediumDynamic Requirebuild/index.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @wdio/browserstack-service@9.39.2.
See all versions of @wdio/browserstack-service for other recorded verdicts.
- Review the evidence and your use of @wdio/browserstack-service@9.39.2 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.