webscraping-expert

SUSPICIOUS: the skill’s general footprint matches web scraping, but it materially escalates into anti-bot evasion, CAPTCHA solving, session/token interception, and credential-bearing HAR handling. Install trust is mostly normal documentation-level risk, but the operational scope and credential capture guidance are high-risk and disproportionate for a generic scraping helper.

The fragment documents and implements systematic probing for alternate routes that may serve data without the anti-bot controls applied to a site's main page. It sends requests using Chrome impersonation and logs response metadata locally; the code contains no evident data theft, destructive behavior, or remote command functionality. Its explicit sign-off and hard-limit warnings mitigate but do not eliminate the risk of enabling unauthorized scraping or access-control circumvention. Severity is moderate; no suspicious fixed domain or IP is present, and the example URL is example[.]com.

This fragment guides a website data-extraction workflow and explicitly solicits curl commands, logged-in HAR files that may contain session cookies, and optionally usernames and passwords. That creates a significant credential and session-data exposure risk; no actual transmission to an external domain or executable malware is shown in the visible text. Severity: security warning; avoid sharing passwords or unsanitized HAR files, and use authorized, appropriately sanitized data only.

This documentation explains how to invoke Salesforce Aura Apex methods and paginate returned records, including anonymous calls and reuse of authenticated sid cookies and aura tokens. It can facilitate unauthorized bulk data access when used without permission, but the supplied text contains no tenant-specific target, credentials, or exfiltration destination and does not itself execute. Severity is moderate due to the potential for data extraction and session misuse; no malware behavior is evident.

This fragment is documentation for identifying anti-bot vendors and evading their protections; its included code only matches response headers, body text, and cookies against regular expressions. The guidance recommends challenge solving, clearance-cookie reuse, browser automation, and residential proxies, which can facilitate access-control circumvention. No malware behavior or data exfiltration is implemented in this fragment; severity is a security concern related to misuse, not a demonstrated infection or system compromise.

This code implements browser-assisted authentication and local session caching, with no evident malware or fixed exfiltration destination. It stores cookies and bearer tokens in plaintext at the configured cache path and may send them to unintended hosts because cookie scope is discarded and Authorization is applied session-wide. Treat this as a security warning: restrict request destinations, preserve cookie domain scope, and protect the cache file; no specific external domain, URL, IP, or environment variable is hardcoded.

This documentation explains how to diagnose and bypass anti-bot protections using impersonation clients, stealth browsers, CAPTCHA solvers, and probes for less-protected routes. It contains no executable behavior, credential theft, or malware indicators. The guidance could facilitate unauthorized circumvention, so use should be limited to authorized testing; overall risk is moderate.