bumble-automation
Fail
Audited by Snyk on Jun 21, 2026
Risk Level: CRITICAL
Full Analysis
HIGH W007: Insecure credential handling detected in skill instructions.
- Insecure credential handling detected (high risk: 1.00). The prompt embeds an actual API key and session cookies and shows code that places them verbatim into headers and constants (e.g., Authorization/anchor-api-key and COOKIES), requiring the LLM to output secret values directly — a high exfiltration risk.
CRITICAL E006: Malicious code pattern detected in skill scripts.
- Malicious code pattern detected (high risk: 1.00). This skill embeds a hard-coded Anchor Browser API key and live Bumble session cookies, includes instructions to extract cookies from a local Chrome CDP, and automates bulk liking and messaging (reading full chat history and logging it), which together enable credential theft, account takeover, mass automated/abusive actions, and potential exfiltration of private messages — high-risk malicious/abusive intent.
MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).
- Third-party content exposure detected (high risk: 0.85). The required runtime workflow uses Playwright to navigate to Bumble pages (e.g.,
page.goto('https://fr1.bumble.com/app')and.../beeline) and then reads DOM text like[data-qa-role="encounters-user"]/ message history viapage.evaluate, which ingests outsider-authored free-form content from Bumble’s web app into the LLM context.
HIGH W008: Secret detected in skill content (API keys, tokens, passwords).
- Secret detected (high risk: 1.00). The file contains multiple high-entropy, usable credentials:
- The Anchor Browser API key (the sk-... string) appears literally in the "Credentials" block and is hardcoded in the script as API_KEY. This is a high-entropy API key (not a placeholder like "sk-xxxx") and can be used to authenticate to the Anchor Browser API.
- The Bumble session cookie block includes high-entropy session tokens (the "session" value and the long "HDR-X-User-id" value). These are session/authentication cookies that would allow access to the Bumble account when presented to the site. Those are not simple/example values and should be treated as secrets.
- Lower-entropy or non-secret items present: "aid" (numeric), "device_id" (UUID-like), and TEMP_API_HOST are not high-entropy secrets for access in this context and can be ignored.
The potential_matches list correctly picked up the sk-... key (duplicated). Because real API tokens and session cookies are present, this file contains live secrets.
Issues (4)
W007
HIGHInsecure credential handling detected in skill instructions.
E006
CRITICALMalicious code pattern detected in skill scripts.
W011
MEDIUMThird-party content exposure detected (indirect prompt injection risk).
W008
HIGHSecret detected in skill content (API keys, tokens, passwords).
Audit Metadata