T08 · Insecure Dependencies
- Location
references/servers-infrastructure.md:117- Finding
Unpinned Third-Party Package Retrieval and Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a broad web-development reference skill with some examples that need normal care, but I found no hidden behavior, executable payloads, or purpose-mismatched actions.
Install only if you want a broad web-development reference skill. Before letting an agent run examples from it, review commands that install packages, deploy to hosting providers, use sudo/systemctl, or touch secrets; prefer pinned package versions, least-privilege environments, and placeholder-only .env examples.
references/servers-infrastructure.md:117Unpinned Third-Party Package Retrieval and Execution
SKILL.md:501Content Security Policy Example Permits Unsafe Inline Scripts
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
Start with basic HTML, enhance with CSS, add JavaScript functionality:
<!-- Base HTML (works without CSS/JS) -->
<form action="/submit" method="POST">
<label for="email">Email:</label>
<input type="email" id="email" name="email" required>
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Landmark roles -->
<nav role="navigation">
<main role="main">
<aside role="complementary">
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).
GET /api/users/1 // Get user POST /api/users // Create user PUT /api/users/1 // Update user DELETE /api/users/1 // Delete user
### GraphQL
The .env snippet demonstrates storing a live-style API credential directly in a file example, which can encourage unsafe secret storage and accidental disclosure through version control, screenshots, logs, or copied templates. Because this file is specifically a web development reference, readers are likely to reuse the pattern verbatim in real projects, increasing the chance of credential exposure.
# .env
DATABASE_URL=postgres://localhost/db
API_KEY=secret-key-here
NODE_ENV=development
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<head>
<!-- Character encoding -->
<meta charset="UTF-8">
<!-- Responsive viewport -->
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).
POST /users # Create user
PUT /users/123 # Update user 123 (full)
PATCH /users/123 # Update user 123 (partial)
DELETE /users/123 # Delete user 123
GET /users/123/posts # List posts by user 123
GET /posts?author=123 # Alternative: filter posts
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Inline SVG -->
<svg width="100" height="100">
<circle cx="50" cy="50" r="40" fill="blue" />
</svg>
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
800px"
alt="Responsive image">
<!-- Pixel density -->
<img src="image.jpg"
srcset="image.jpg 1x,
image@2x.jpg 2x,
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Picture element for art direction -->
<picture>
<source media="(min-width: 1024px)" srcset="large.webp" type="image/webp">
<source media="(min-width: 768px)" srcset="medium.webp" type="image/webp">
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- DNS prefetch -->
<link rel="dns-prefetch" href="//example.com">
<!-- Preconnect (DNS + TCP + TLS) -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<!-- Prefetch (low priority for next page) -->
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
1. Client redirects to auth server
2. User authenticates and grants permission
3. Auth server redirects back with code
4. Client exchanges code for access token
5. Client uses token to access resources
#### 4. Multi-Factor Authentication (MFA)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Configuration without hardcoding.
# .env file
DATABASE_URL=postgresql://localhost/mydb
API_KEY=secret-key-here
NODE_ENV=production
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Configuration without hardcoding.
# .env file
DATABASE_URL=postgresql://localhost/mydb
API_KEY=secret-key-here
NODE_ENV=production
The skill description is extremely broad, covering nearly all web development, networking, security, infrastructure, and terminology tasks. In agent-routing systems, such breadth can cause over-triggering, leading this skill to activate in many ordinary conversations and unnecessarily import strong behavioral instructions that may override more task-appropriate defaults.
The 'When to Use This Skill' section enumerates many broad triggers without boundaries, making invocation likely across a wide range of normal web-related prompts. This increases prompt-scope risk because the agent may apply this skill's persona and workflow even when a narrower or safer skill would be more appropriate.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
# Initialize project
npm init
npm init -y # Skip prompts
# Install dependencies
npm install package-name
The documentation includes a .env example with API_KEY=secret-key-here but gives no warning that API keys are sensitive, should never be committed, and must be sourced from a secret manager or local untracked environment file. In a developer reference, this can normalize insecure credential handling and lead users to copy the pattern directly into repositories or shared examples.
Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.
DATABASE_URL=postgres://localhost/db API_KEY=secret-key-here NODE_ENV=development
```javascript
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.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Let's Encrypt (Free):
# Certbot
sudo certbot --nginx -d example.com
Cloudflare (Free with Cloudflare DNS)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Let's Encrypt (Free):
# Certbot
sudo certbot --nginx -d example.com
Cloudflare (Free with Cloudflare DNS)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Let's Encrypt (Free):
# Certbot
sudo certbot --nginx -d example.com
Cloudflare (Free with Cloudflare DNS)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Let's Encrypt (Free):
# Certbot
sudo certbot --nginx -d example.com
Cloudflare (Free with Cloudflare DNS)
No suspicious patterns detected.