ClawHub

Efka Api Integration

Security checks across malware telemetry and agentic risk

Overview

This is a purpose-aligned EFKA payroll and social-security skill, but it handles sensitive government credentials and employee payroll data that require careful controls.

Install only in an environment where EFKA credentials and /data/efka/ are restricted to trusted payroll operators. Keep the four-eyes approval requirement mandatory for submissions and employee-record changes, review generated APD and lifecycle files before upload, avoid sending PII to Slack or calendars, and do not run the sudo dependency command unless it matches your organization's approved provisioning process.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (7)

Intent-Code Divergence

Medium
Confidence
89% confidence
Finding
The skill repeatedly states that all EFKA submissions require human approval, yet the examples present submission-related actions as already completed, which normalizes direct filing without an explicit approval gate. In a payroll/social-security context handling legally significant submissions, this inconsistency can lead operators or downstream tooling to bypass required review and submit regulated data prematurely or incorrectly.

Intent-Code Divergence

Medium
Confidence
84% confidence
Finding
The deployment section claims there are no external API dependencies requiring complex authentication, but the skill clearly depends on EFKA credentials and optionally integrates with Slack and Google Calendar. This mismatch can mislead users into underestimating the external connectivity, authentication, and data-exposure surface of the skill, resulting in insecure deployment assumptions.

Vague Triggers

Medium
Confidence
91% confidence
Finding
The eval prompts authorize high-impact payroll, employee registration, termination handling, and batch declaration workflows without clear gating such as required human approval at execution time, validation prerequisites, or explicit limits on external actions. In a payroll/social-security integration, overly broad task framing can cause an agent to perform regulated calculations, update records, generate filing-ready artifacts, or prepare submissions from unverified input, increasing the chance of unauthorized or incorrect compliance actions.

Missing User Warnings

Medium
Confidence
86% confidence
Finding
The skill requests EFKA credentials and advertises webhook/calendar integrations but does not prominently warn that it handles highly sensitive employee payroll and identity data. Without strong handling guidance, users may configure third-party notifications or external services in ways that leak regulated personal or financial information beyond intended boundaries.

Missing User Warnings

Medium
Confidence
81% confidence
Finding
The documented file-watching and auto-processing workflow can automatically ingest and modify sensitive employee payroll records, yet the skill does not foreground the operational risk of unattended processing. In this context, malformed, malicious, or misrouted files could trigger unauthorized updates, incorrect calculations, or preparation of submissions without adequate human review.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The onboarding example exposes full AFM, AMKA, street address, and salary information in clear text, effectively normalizing display of highly sensitive PII and payroll data. Such examples can be copied into logs, tickets, demos, or terminal history, increasing the likelihood of privacy violations, identity fraud, and noncompliance with GDPR or local employment-data protections.

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
91% confidence
Finding
| sudo

VirusTotal

60/60 vendors flagged this skill as clean.

View on VirusTotal