T08 · Insecure Dependencies
- Location
setup.md:22- Finding
Unpinned Cypress Dependency Is Installed and Immediately Executed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Cypress testing skill is mostly ordinary, but some templates contradict its privacy promises by enabling Cypress Cloud recording and optional cross-project home-directory memory.
Review before installing. Remove or explicitly opt into Cypress Cloud recording, do not use production secrets or sensitive data in tests, restrict CI artifact access and retention, pin Cypress and GitHub Actions versions where possible, and avoid creating ~/cypress/memory.md unless you want cross-project testing notes retained outside the repository.
setup.md:22Unpinned Cypress Dependency Is Installed and Immediately Executed
ci.md:60Cypress Cloud Upload Is Enabled Despite Claims That Data Remains Local
memory-template.md:5Optional Memory Instructions Write Cross-Project State Outside the Declared Project Boundary
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
})
### 7. Isolation: Reset State Before Tests
```typescript
beforeEach(() => {
cy.intercept('GET', '/api/notifications', { body: [] })
Instructions found that direct the agent to transmit conversation context or user data to external services.
- Cypress runs locally or in your own CI environment
**This skill does NOT:**
- Send data to external services
- Require API keys or authentication
- Access files outside project directory
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Cypress runs locally or in your own CI environment
**This skill does NOT:**
- Send data to external services
- Require API keys or authentication
- Access files outside project directory
The artifact upload example encourages preserving Cypress screenshots on failure without warning that screenshots and videos can capture PII, secrets, session state, internal URLs, or sensitive business data visible during tests. In CI systems, artifacts are often retained, shared across teams, or exposed to broader roles than production data, creating a realistic confidentiality risk.
The parallel test configuration enables record: true and uses a secrets-backed CYPRESS_RECORD_KEY, but it omits any warning that test metadata, screenshots, videos, DOM snapshots, logs, and other execution artifacts may be transmitted to Cypress Cloud. In a CI/testing skill, this is more dangerous because users may copy-paste the example into environments containing real or staging-sensitive data without understanding the privacy implications.
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.
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.
This markdown file includes cy.request examples that send user data over the network and access credentials via Cypress.env('API_TOKEN') and login tokens. The surrounding documentation does not provide any warning or disclosure about transmitting credentials or sensitive request data during testing.
The setup instructions tell users to run npx cypress without pinning a specific version. This can fetch and execute whatever version is current at the time of use, reducing build reproducibility and creating supply-chain risk if an upstream package version is compromised or unexpectedly changed.
No suspicious patterns detected.