T09 · Insecure Skill Coding Practices
- Location
linkedin_scraper.py:325- Finding
Untrusted LinkedIn Content Is Returned to the AI Agent Without an Explicit Trust Boundary
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed LinkedIn job-search and monitoring helper that stores local search state but does not show credential theft, hidden execution, or destructive behavior.
Install only if you are comfortable with the skill making LinkedIn web requests and saving your job-search profiles/history locally. Use recurring monitoring only after confirming the exact cron or OpenClaw schedule it creates and how to disable it, and treat all job listing text as untrusted external content.
linkedin_scraper.py:325Untrusted LinkedIn Content Is Returned to the AI Agent Without an Explicit Trust Boundary
requirements.txt:1Third-Party Dependencies Are Not Reproducibly Pinned
The core declared capability of searching LinkedIn job listings with city-based filters is accurately represented: the code supports keyword search, location text or geo ID lookup, date/experience/job-type/remote filters, and a geo_ids file consistent with broad city coverage. However, the description also claims monitoring with hourly cron support and smart deduplication. This code chunk contains no scheduler, cron integration, persistent state, prior-run comparison, or duplicate suppression. It simply executes a single scrape when run and returns results. Therefore the description overstates important capabilities beyond what the supplied code actually does.
The README instructs users to have the agent set up automated monitoring and says it will configure an appropriate cron schedule, but it does not clearly warn that this may modify the user's system task scheduler. In an agentic environment, silent persistence or background task creation is security-relevant because users may not realize the skill can establish recurring execution on their machine.
The skill instructs the agent to use Python scripts, recurring cron behavior, config files, and web scraping, which imply network access and local file read/write, but it does not declare any explicit tool scope or allowed-tools boundaries. This is dangerous because an agent/runtime may grant broader capabilities than users expect, increasing the chance of unintended file persistence or network activity without clear consent or sandboxing constraints.
The skill promotes hourly monitoring but does not clearly warn users that it will perform recurring network scraping and persist search profiles/history locally. This is dangerous because users may unknowingly authorize ongoing background activity and data retention, creating privacy, compliance, and consent risks beyond a one-time search.
The user-intent mapping is broad enough that ordinary job-search phrases could automatically trigger scraping, profile creation, or recurring monitoring actions without explicit confirmation. This is dangerous because it can cause unintended network requests and persistent state changes, especially when moving from a one-time search intent to ongoing automated monitoring.
The manifest describes a job search/monitoring skill with cron and deduplication, but this file implements a fuller local profile-management CLI that persists and deletes configuration/history data. While related to monitoring, these mutating administrative operations go beyond the narrow wording of 'search and monitor LinkedIn job listings.'
This code forces requests to use the en-US/en locale via a fixed HTTP header. Under the natural-language policy rule, locale constraints should not be imposed unless the user is given a choice or the restriction is clearly justified as region-specific.
The dependency is specified with a lower bound only, which makes builds non-reproducible and can lead to different versions being installed over time. That increases supply-chain risk and makes it difficult to verify whether a vulnerable or incompatible release of requests is being used.
requests>=2.28.0
beautifulsoup4>=4.11.0
The manifest references requests without pinning an exact version, and requests has multiple known advisories affecting some releases. Because the installed version is not fixed, the deployment could resolve to an affected version, leaving the skill exposed to known issues such as credential leakage or other request-handling flaws.
beautifulsoup4 is also unpinned, so installations may resolve to different versions across environments or at different times. This weakens reproducibility and can expose the skill to future vulnerable releases or unexpected behavior changes without any code change.
requests>=2.28.0
beautifulsoup4>=4.11.0