Back to skill

Security audit

maternity-leave-planner

Security checks for vulnerabilities and agentic risk

Overview

This local planning tool shows no harmful system behavior, but its leave-pay and job-protection calculations contain reproducible errors.

Use this as a rough worksheet only. Independently confirm protected leave dates, partner eligibility, benefit overlap, and payment totals with HR and the relevant state program before scheduling leave or budgeting. The verified calculation errors warrant caution, but do not establish malicious behavior or excessive system access.

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
  • Memory PoisoningPersistent Context Injection, Context Window Stuffing, Memory Manipulation
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Memory Manipulation

High
Category
Memory Poisoning
Confidence
85% confidence
Finding

Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.

Content

Scanner excerpt · scripts/maternity_plan.py (reported line 142)May include surrounding context.

python
take = i < int(rec_wk)  # overlapping recovery: employer tops up to 100%
        b = max(0.0, pay_wk - (state_benefit_weekly(pay_wk, state)[0] if p else 0.0)) if (p and take) else pay_wk
        src = "employer policy (top-up)" if (p and take) else "employer policy"
        # replace state pay in this recovery/bonding week rather than adding
        if take and weeks and weeks[-1][2] == "recovery":
            w = weeks[-1]
            weeks[-1] = (w[0], w[1], w[2], w[3] + " + " + src, pay_wk, 1.0, w[6])

The plan labels weeks as job-protected without applying the FMLA eligibility verdict or consistently enforcing protection limits.

High
Category
Excessive Agency
Confidence
99% confidence
Finding

The FMLA eligibility verdict only affects a warning; it is not passed into build_plan, which independently labels weeks as FMLA- or state-protected without consistently enforcing eligibility or duration limits. In a leave-planning skill, these authoritative-looking weekly labels can cause users to take unprotected leave and risk losing employment or benefits, despite the general disclaimer.

Content

No source excerpt is available for this finding.

Non-birthing and adoptive parents are assigned childbirth-recovery disability benefits.

Medium
Category
Excessive Agency
Confidence
99% confidence
Finding

The partner flag suppresses pre-birth benefits but does not suppress childbirth-recovery weeks or disability payments. Non-birthing and adoptive parents therefore receive plans that overstate available paid leave, creating financial and employment-planning risks in the skill's core use case.

Content

No source excerpt is available for this finding.

Employer leave is documented as substituting for state bonding, but the planner appends the full state bonding entitlement afterward.

Medium
Category
Excessive Agency
Confidence
98% confidence
Finding

Although the code describes employer leave as substituting for state bonding, it can append employer bonding weeks and then append the full state bonding entitlement without accounting for concurrency. Where employer and state benefits must run together, the resulting plan overstates paid leave duration and compensation; the financial-planning context makes this a consequential correctness defect rather than evidence of malicious behavior.

Content

No source excerpt is available for this finding.