adspower-browser
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill is coherent for AdsPower management, but it can use API-key access to read cookies/credentials and delete or share browser profiles, so it needs user review.
Install only if you trust the external adspower-browser npm package and need agent control of AdsPower. Treat the AdsPower API key, cookies, passwords, proxy credentials, and 2FA keys as sensitive. Require explicit confirmation with exact profile IDs before reading cookies, deleting profiles, wiping cache/history, closing all profiles, sharing profiles, or running page JavaScript.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent with this key can act against the user's AdsPower local API with the authority that key grants.
The skill explicitly uses an AdsPower API key for local API control, but the registry metadata declares no primary credential or required environment variables.
Pass `--port` / `--api-key` when needed, or set the `ADS_API_KEY` environment variable before running `start`.
Declare and treat the AdsPower API key as sensitive; only provide it when you trust the CLI and intend the requested operation.
A mistaken or overbroad request could expose web-account sessions or credentials stored in AdsPower profiles.
The skill handles account passwords, cookies, and 2FA-style key material, and can retrieve profile cookies, which can function as reusable login sessions. The artifacts do not specify output handling or require confirmation before cookie retrieval.
At least one of **username**, **password**, **cookie**, **fakey** (required): Account information. ... **get-profile-cookies** — Query cookies of the specified profile.
Require explicit user approval and exact profile IDs before reading cookies or handling account credentials, and avoid returning or storing cookies unless strictly necessary.
Profiles could be deleted or shared to another account if the agent interprets a request too broadly or uses the wrong IDs or receiver.
The skill documents destructive and transfer operations over AdsPower profiles, including batch sharing, without adding an explicit confirmation, rollback, or narrow-scope requirement.
**delete-browser** — Delete the browser(s). ... **share-profile** — Share profiles via account email or phone. Max 200 per request.
Before delete, cache-wipe, close-all, or share operations, require a clear user confirmation that includes the exact profile IDs and destination account.
The installed CLI will handle AdsPower API access and profile data, so a compromised or unexpected package version would be high impact.
The skill depends on a globally installed external npm package whose code is not included in the artifact scan and is not pinned in the instruction.
npm install -g adspower-browser
Install only from a trusted npm source, pin or verify the package version, and review the package before providing API keys or profile data.
Running untrusted JavaScript in a logged-in browser profile could read or change page state and account data.
The referenced automation map includes a raw page-script execution capability. This can be legitimate for browser automation, but it is powerful when used inside authenticated AdsPower profiles.
`evaluate-script` | Run JavaScript in the page context.
Use script evaluation only with trusted code and explicit user approval, preferably after safer targeted automation commands have been considered.
The AdsPower runtime may continue running with API access until stopped.
The skill can start a local AdsPower runtime and also documents stop/status commands. This is disclosed and purpose-aligned, but users should be aware of the long-running local control surface.
ads start -k <KEY> # Start the adspower runtime ... ads stop # Stop the adspower runtime
Stop the runtime when finished and avoid leaving API-key-enabled headless sessions running unnecessarily.