T09 · Insecure Skill Coding Practices
- Location
scripts/xianyu-login.js:3- Finding
Undocumented Hard-Coded Phone Number Submitted Through an SMS Authentication Flow
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This scraping skill mostly matches its purpose, but it includes undocumented login/SMS automation and unsafe browser settings that need review before use.
Install only if you trust the publisher and will run it in a restricted environment. Use it only on sites you are authorized to access, avoid scraping sensitive pages unless needed, treat screenshots/HTML/cookies as secrets, and do not run the Xianyu login script unless the phone number is yours and you explicitly intend to request an SMS code. Prefer container or network isolation for browser runs, and pin or review any external skill or dependency before installing.
scripts/xianyu-login.js:3Undocumented Hard-Coded Phone Number Submitted Through an SMS Authentication Flow
scripts/xianyu-stealth.js:12Chromium Sandbox and Web Security Boundaries Are Disabled for Untrusted Pages
scripts/playwright-simple.js:11Unrestricted URL Navigation Enables Server-Side Request Forgery and Internal Network Access
package-lock.json:18Dependency Archive Is Retrieved Through a Cleartext HTTP Registry Mirror
SKILL.md:87Documentation Instructs Users to Install and Execute an Unpinned External Skill
The declared description emphasizes anti-bot protection and suitability for complex sites with scraping defenses. The code does not implement any anti-bot evasion measures such as stealth plugins, header/cookie management, proxy rotation, challenge solving, session handling, or browser fingerprint masking. In fact, the code comments explicitly describe it as a 'simple' scraper for general dynamic sites with no anti-scraping protection. It only performs basic navigation, a fixed delay, content extraction, and optional screenshot capture. Therefore the description materially overstates the capability and intended use compared with the actual behavior.
The declared description says this is a Playwright-based web scraping skill with anti-bot protection. While the code does use Playwright and includes anti-detection measures, its primary behavior is not scraping content. Instead, it automates a login process on Xianyu/Goofish: visiting the site, clicking a login button, filling a phone number, attempting to send an SMS verification code, taking screenshots, and displaying page text. These are materially different capabilities from scraping and involve account-authentication actions that were not declared. Therefore the description does not accurately represent the code's actual behavior.
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
Referenced artifact was not completely inspected
| **Cloudflare Protected** | High | **Playwright Stealth** ⭐ | `scripts/playwright-stealth.js` |
The README suggests manually logging in and exporting cookies without any safety guidance for handling authentication material. Exported cookies can enable session hijacking or unauthorized account access if copied, logged, shared, or stored insecurely, and this risk is especially relevant in a scraping skill that may target authenticated sessions.
This script goes beyond ordinary scraping and automates an account login flow, including entering a hardcoded phone number and triggering SMS verification. In a scraping skill, that creates credential-handling and account-access capabilities that can be misused for unauthorized access attempts, account takeover workflows, or deceptive collection of one-time codes.
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
echo ""
# 清理
rm -f /tmp/test-*.json screenshot-*.png
echo "✅ 所有測試通過!"
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The README explicitly promotes anti-bot evasion techniques and page data capture without any warning about authorization, terms-of-service, privacy, or sensitive-data handling. In a scraping skill, that omission increases the chance of misuse against protected sites and unsafe retention of scraped HTML or screenshots that may contain personal or confidential information.
The README explicitly promotes stealth scraping, hiding automation fingerprints, screenshot capture, and HTML saving, but provides no warning about authorization, privacy, or lawful data handling. In a scraping skill, that omission increases the likelihood of misuse against protected sites or collection of sensitive content, especially because the text frames bypassing anti-bot controls as a recommended workflow.
The skill documents executable commands that use network access and environment variables, but it does not declare any explicit tool scope or permissions metadata. In a skill ecosystem, missing scope declarations weakens reviewability and can let users or orchestration systems invoke higher-risk behaviors without clear consent boundaries.