Back to skill

Security audit

ia-nodejs-backend

Security checks for vulnerabilities and agentic risk

Overview

The verdict is benign with medium confidence: the scanners report mostly documentation for Node.js backend development, but flag a possible mismatch because the instructions also describe running evaluation and diagnostic commands for the skill.

The verdict is benign, but confidence is medium and the Skillspector scan is partial: it reports one missing local path-like reference, so coverage is incomplete. Before installing, consider whether evaluation and diagnostic commands belong in a backend-development skill and whether the unpinned `npx tsc` reference is acceptable; benign does not mean risk-free.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The supplied commands perform evaluation and diagnostic operations on a named skill rather than providing or implementing backend development patterns. This is a materially different visible purpose, not merely a supporting backend implementation detail. The Python script's internal behavior is not supplied, so no additional capabilities or side effects can be established.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/security.md (reported line 7)May include surrounding context.

md
## Authentication Pattern

- **Access token**: JWT, 15min expiry, payload: `{ userId, email }`
- **Refresh token**: JWT, 7d expiry, stored in DB (revocable)
- **Passwords**: bcrypt (10+ rounds) or argon2
- **Middleware**: extract `Bearer` token → `jwt.verify` → attach `req.user` → `next()`

Unrestricted Tool Access

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.

Content

Scanner excerpt · references/security.md (reported line 43)May include surrounding context.

md
sories only*, not a freshly-malicious or typosquatted package. Harden the install itself:

- **Frozen installs.** Commit the lockfile and install with the manager's immutable mode (`npm ci`, `pnpm install --frozen-lockfile`, `yarn install --immutable`) so CI can't silently resolve a different tree.
- **Gate lifecycle scripts.** Block dependency `preinstall`/`postinstall` scripts by default and approve them per-package via the manager's native policy, so a compromised transitive dependency can't run arbitrary code at install time. Verify the exact manager- and version-specific flag in current official documentation. Prefer Context7 when available; otherwise read the package manager's official docs with available web tools.
- **Release-age floor.** Configure the manager to refuse versions published more recently than a cooldown window set by team policy, in days (pnpm `minimumReleaseAge` in minutes, npm `min-release-age` in days), so a freshly published malicious version is not installed

MCP server referenced without pinned version: 'npx tsc'.

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

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.

Content

No source excerpt is available for this finding.