Back to skill

Security audit

primevue

Security checks for vulnerabilities and agentic risk

Overview

This PrimeVue documentation skill is mostly coherent, but one install example could lead users to install unrelated npm packages and another uses mutable CDN JavaScript.

Review and correct the dependency examples before use. Prefer installing official PrimeVue packages only with a lockfile, avoid generic component package names, and pin any CDN script with integrity or bundle dependencies through your package manager.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (2)

T08 · Insecure Dependencies

Warning
Location
references/components.md:11
Finding

Unrelated Top-Level npm Packages Recommended as PrimeVue Components

Content
View full analysis

Vulnerability Details

File Location: references/components.md:11
Vulnerability Type: Dependency confusion and unnecessary third-party package installation
Risk Level: Medium

Vulnerable Code:

bash
npm install primevue button inputtext textarea select checkbox radiobutton

Technical Analysis

The documentation recommends installing generic top-level npm packages such as button, inputtext, textarea, and select as if they were individually distributed PrimeVue components. PrimeVue components are normally imported from subpaths of the primevue package, such as primevue/button; they do not require these generic packages to be installed separately.

Generic package names may refer to unrelated third-party projects and unnecessarily expand the dependency graph. During installation, npm may execute package lifecycle scripts such as preinstall, install, or postinstall. If any named package or transitive dependency is malicious or later compromised, code can execute with the privileges of the user running npm.

This is a documentation-triggered supply-chain risk rather than automatic execution by the Skill itself. Exploitation requires a user to follow the affected installation command.

Attack Path

  1. A developer follows the documented tree-shaking installation command.
  2. npm resolves the generic package names from the configured package registry.
  3. Unrelated or compromised packages and their transitive dependencies are downloaded.
  4. Package lifecycle scripts execute during installation unless explicitly disabled.
  5. Malicious code can modify the project, access files available to the developer account, read environment variables, or establish network connections.

Impact Assessment

A malicious dependency could execute with the local privileges of the developer or CI account running npm install. Potential scope includes the current project, user-readable files, environ ...[truncated 166 chars]

Remediation
View remediation

Remediation Suggestions

Replace the affected command with installation of the official PrimeVue package only:

bash
npm install primevue

Import individual components through PrimeVue subpaths for tree-shaking:

javascript
import Button from 'primevue/button';
import InputText from 'primevue/inputtext';
import Textarea from 'primevue/textarea';
import Select from 'primevue/select';
import Checkbox from 'primevue/checkbox';
import RadioButton from 'primevue/radiobutton';

Additionally:

  • Commit and enforce a reviewed lockfile.
  • Use npm ci in CI environments.
  • Review dependency provenance and lifecycle scripts.
  • Consider disabling lifecycle scripts during untrusted dependency analysis with npm install --ignore-scripts.
  • Use an isolated, least-privileged CI environment for package installation.

T08 · Insecure Dependencies

Warning
Location
SKILL.md:180
Finding

Unpinned Third-Party CDN Script Without Subresource Integrity

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:180
Vulnerability Type: Mutable external JavaScript dependency
Risk Level: Medium

Vulnerable Code:

html
<script src="https://unpkg.com/primevue/umd/primevue.min.js"></script>

Technical Analysis

The CDN example loads executable JavaScript from an external URL without an exact version or Subresource Integrity hash. Because the URL is mutable, the content delivered to users can change after this Skill has been reviewed. The consuming application therefore trusts the CDN, package publisher, DNS and TLS infrastructure, and the current package release state at runtime.

If the upstream package, publisher account, CDN, or delivery path is compromised, altered JavaScript can be returned and executed by the browser. The lack of an integrity attribute prevents the browser from verifying that the response matches a previously reviewed artifact.

This issue does not cause the Skill itself to retrieve or execute the script. Exploitation requires a developer to copy the example into an application and a user to load the resulting page.

Attack Path

  1. A developer embeds the documented CDN script URL in an application.
  2. The application loads the script whenever a user visits the affected page.
  3. The upstream package or CDN response changes, whether through compromise, malicious publication, or an incompatible update.
  4. The browser downloads the changed JavaScript because no exact reviewed artifact or integrity hash is enforced.
  5. The browser executes the response in the application page context.

Impact Assessment

Altered CDN JavaScript would execute with the browser privileges available to scripts on the consuming page. Depending on the application's security controls, it could access page content, manipulate the DOM, read non-HttpOnly browser storage, make same-origin requests using the user's active session, capture user input, or ex ...[truncated 153 chars]

Remediation
View remediation

Remediation Suggestions

Prefer installing and bundling a reviewed version through the project's package manager and lockfile. If CDN delivery is required:

  • Pin the URL to an exact reviewed package version.
  • Generate and specify a Subresource Integrity hash.
  • Add crossorigin="anonymous" when using SRI with a cross-origin resource.
  • Configure a restrictive Content Security Policy.
  • Periodically review and intentionally update the pinned artifact and integrity hash.
  • Consider self-hosting the verified JavaScript asset.

A hardened example should follow this pattern, using a real version and hash generated from the selected artifact:

html
<script
  src="https://unpkg.com/primevue@EXACT_VERSION/umd/primevue.min.js"
  integrity="sha384-REVIEWED_ARTIFACT_HASH"
  crossorigin="anonymous"></script>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 188)May include surrounding context.

md
- [Components](references/components.md)

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/theming.md (reported line 260)May include surrounding context.

$dt Utility

Access token values programmatically:

vue
import { $dt } from '@primeuix/themes';

Session Persistence

Medium
Category
Rogue Agent
Confidence
75% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

Scanner excerpt · references/components.md (reported line 474)May include surrounding context.

vue
<Stepper value="1">
    <StepList>
        <Step value="0">Step 1</Step>
        <Step value="1">Step 2</Step>
        <Step value="2">Step 3</Step>

Session Persistence

Medium
Category
Rogue Agent
Confidence
75% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

Scanner excerpt · references/components.md (reported line 478)May include surrounding context.

vue
<Stepper value="1">
    <StepList>
        <Step value="0">Step 1</Step>
        <Step value="1">Step 2</Step>
        <Step value="2">Step 3</Step>

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The InputNumber example specifies locale="en-US", which forces a specific locale in natural-language-facing formatting. The file does not indicate that this is only an illustrative placeholder, nor does it offer user choice or a justification for restricting locale.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

This markdown file includes FileUpload examples that send selected files to /api/upload, which can affect user data and privacy. The surrounding documentation provides no user warning or disclosure that files may be transmitted off-device or to a backend service.

Content

No source excerpt is available for this finding.