ClawHub
Back to skill

Security audit

Efka Api Integration

Security checks for vulnerabilities and agentic risk

Overview

This EFKA payroll skill is mostly purpose-aligned, but it needs review because it handles credentials and regulated payroll submissions while its approval and external-access boundaries are inconsistent.

Install only after confirming whether EFKA submission and payment commands are dry-run by default, how four-eyes approval is technically enforced, and how EFKA credentials and employee identifiers are protected. Avoid putting real EFKA passwords in shared shell history or committed files, and treat any submission, registration, payment, Slack, or calendar workflow as potentially live until proven otherwise.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (6)

Chaining Abuse

High
Category
Tool Misuse
Content
export OPENCLAW_DATA_DIR="/data"
export EFKA_USERNAME="your-efka-username"
export EFKA_PASSWORD="your-efka-password"
which jq curl || sudo apt install jq curl
```

EFKA credentials are required only for submitting social security declarations. Payroll calculations and contribution processing work offline. All government submissions require human approval (four-eyes workflow).
Confidence
75% confidence
Finding
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
The document states there are no external API dependencies requiring complex authentication, yet it also requires EFKA credentials and references curl-based government submissions. This inconsistency can mislead reviewers and operators about the trust boundary, causing the skill to be deployed with insufficient scrutiny for credential handling and outbound data transmission.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The setup and surrounding documentation involve EFKA credentials and highly sensitive employee identifiers, but there is no strong privacy or secret-handling warning. In a payroll and social-security context, this increases the chance that users expose credentials in shell history, logs, screenshots, or shared artifacts, and mishandle regulated personal data.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Content
export OPENCLAW_DATA_DIR="/data"
export EFKA_USERNAME="your-efka-username"
export EFKA_PASSWORD="your-efka-password"
which jq curl || sudo apt install jq curl
```

EFKA credentials are required only for submitting social security declarations. Payroll calculations and contribution processing work offline. All government submissions require human approval (four-eyes workflow).
Confidence
82% confidence
Finding
The setup instructs users to run 'sudo apt install jq curl' directly from the skill documentation. Even though the packages are common, encouraging privileged installation from within skill instructions expands the blast radius of mistakes and conditions users to grant elevated privileges during setup without separate verification.

Description-Behavior Mismatch

Medium
Confidence
94% confidence
Finding
The skill claims all EFKA submissions require human approval, but the examples show submissions, registrations, and payment scheduling as already completed with no visible approval gate. In an automation context, this kind of contradictory guidance can normalize unsafe implementation and lead operators or downstream agents to trigger regulated external actions without the required four-eyes review.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The examples depict external side effects such as EFKA registration submission, payment scheduling, and government file generation without prominent warnings that these actions may transmit real employee data or trigger regulatory events. In a financial-compliance skill, that omission materially raises the risk of accidental live submissions and unintended disclosure of sensitive payroll information.

Static analysis

No suspicious patterns detected.