Back to skill

Security audit

Bazi Fortune Analysis

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent BaZi fortune-analysis instruction skill with no executable code, persistence, or hidden system access, though it asks users for personal birth details.

Install only if you are comfortable sharing birth details for fortune analysis. Treat outputs, especially health, marriage, finance, or life-event predictions, as cultural or entertainment guidance rather than professional advice.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger keywords are broad and include generic terms like 'fortune' and 'astrology', which can cause the skill to activate during unrelated conversations. This increases the chance of unintended routing, exposing users to unnecessary collection of sensitive birth and location data and reducing reliability of agent behavior.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The workflow explicitly asks for birth date, time, place, and gender, which together constitute sensitive personal data and can uniquely identify a person or enable profiling. Although the skill says to respect privacy, it does not clearly warn users why this data is sensitive, how it will be used, or encourage minimization before collection.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.