@wdio/browserstack-service@9.36.0
WebdriverIO service for better Browserstack integration
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not confirmed malicious: the behavior is confined to its BrowserStack runtime flow and there is no install hook or demonstrated theft. However, automatically executing an unverified remotely supplied binary is an unresolved dangerous capability.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running WebdriverIO with this BrowserStack service enabled.
Impact
A compromised update response or configured binary URL could cause execution of an untrusted native binary.
Mechanism
Remote CLI update, local extraction, and child-process execution.
AI rationale
The package is not confirmed malicious: the behavior is confined to its BrowserStack runtime flow and there is no install hook or demonstrated theft. However, automatically executing an unverified remotely supplied binary is an unresolved dangerous capability.
Evidence
build/index.jsbuild/cleanup.js~/.browserstack/cli/binary-*
Network endpoints1
api.browserstack.com
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- At service runtime, the updater accepts a binary URL returned by its update service and can replace it with an environment-supplied URL.
- The service resolves that CLI path and spawns it as a child process.
- The package has no npm install lifecycle hook; this behavior requires service runtime.
Evidence against
- The binary-management behavior is tied to the BrowserStack service bootstrap rather than package installation.
- No source evidence of secret harvesting, unrelated file collection, destructive project changes, or reviewer manipulation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggedbuild/cleanup.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @wdio/browserstack-service@9.35.3
matchedIdentity = npm:[redacted]:9.35.3
similarity = 0.750
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
build/cleanup.jsView on unpkg379import util, { promisify } from "node:util";
L380: import { exec } from "node:child_process";
L381: 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",
...
L353: if (!res.ok) {
L354: throw new ResponseError(`Error response from server ${res.status}: ${await res.text()}`, res);
L355: }
...
L358: function _fetch(input, init) {
L359: const proxyUrl = process.env.HTTP_PROXY || process.env.HTTPS_PROXY;
L360: if (proxyUrl) {
Findings
1 Critical4 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltabuild/cleanup.js
HighChild Processbuild/cleanup.js
HighShell
HighCommand Output Exfiltrationbuild/index.js
HighCross File Remote Execution Contextbuild/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @wdio/browserstack-service@9.36.0.
See all versions of @wdio/browserstack-service for other recorded verdicts.
- Review the evidence and your use of @wdio/browserstack-service@9.36.0 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.