T09 · Insecure Skill Coding Practices
- Location
SKILL.md:57- Finding
Unsafe Extraction and Storage of LinkedIn Session Credentials
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 57–62
Vulnerability Type: Exposure of reusable authentication credentials
Risk Level: MediumVulnerable Code
markdown ## Session Cookie Method (Advanced) If browser relay isn't available, extract the `li_at` cookie from browser: 1. Open LinkedIn in browser, log in 2. DevTools → Application → Cookies → linkedin.com 3. Copy `li_at` value 4. Store securely for API requestsTechnical Analysis
The Skill instructs users to manually extract LinkedIn's
li_atcookie and retain it for API requests. This cookie is a reusable authenticated session credential that can permit access to the user's LinkedIn session without requiring the account password for every request.Copying the credential removes it from the browser's normal cookie-handling protections. The instructions do not define an approved secret-storage mechanism, restrict which processes or destinations may receive the value, prohibit its inclusion in prompts and logs, or establish rotation and deletion procedures. Consequently, the credential may be exposed through clipboard history, terminal history, Agent context, logs, unencrypted files, or other unspecified storage.
The audit found no evidence that the Skill itself transmits the cookie to an attacker. The risk arises from the insecure credential-handling workflow it prescribes.
Attack Path
- The user follows the documented fallback procedure and retrieves the
li_atcookie through browser developer tools. - The user copies the cookie into the system clipboard.
- The credential is pasted into an Agent prompt, command, log, configuration file, or other storage that lacks suitable secret protections.
- A malicious process, unauthorized user, compromised extension, leaked log, or unintended recipient obtains the cookie.
- The exposed cookie is replayed against LinkedIn while the session remains valid.
- The attacker gains access within the authorization sc ...[truncated 910 chars]
- The user follows the documented fallback procedure and retrieves the
- Remediation
View remediation
Remediation Suggestions
- Remove the manual
li_atcookie-extraction workflow and retain authentication inside the attached or isolated browser profile. - Use browser-mediated automation so the session credential is not exposed to the Agent, clipboard, prompts, shell commands, or logs.
- If direct credential handling is operationally unavoidable, store the cookie only in an approved encrypted secret manager with strict access controls.
- Prevent secret values from being printed, logged, serialized into conversation history, or placed in plaintext configuration and temporary files.
- Restrict credential access to the minimum process and destination required, and permit its use only with LinkedIn endpoints.
- Define explicit expiration, rotation, revocation, and secure deletion procedures.
- Warn users that the cookie is equivalent to an active authenticated session and must never be shared.
- Revoke affected LinkedIn sessions immediately if accidental disclosure is suspected.
- Remove the manual
