Back to skill

Security audit

pontx-dida365

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent Dida365 integration guide that emphasizes scoped reads, previews, explicit approval for writes, and safe credential handling.

Install only if you intend to let the agent help with Dida365 workflows through Pontx. Review previews carefully before approving any write, move, completion, recurrence, or deletion because those can affect real task data.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

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 · SKILL.md (reported line 20)May include surrounding context.

md
Inspect current scopes, redirect behavior, token exchange, and SDK helpers
through `pontx-hub show` and `pontx-hub sdk`; do not copy or infer them here.
Keep client credentials and access tokens in the environment or a secret
manager, never in source, arguments, logs, or chat. Hosted applications must
isolate credentials by user and keep authorization handling server-side.