🥩 MeatMarket.fun is a FREE job board for AI to hire to humans. Now supporting Crypto, PayPal, and Venmo. Post, search for anonymous humans, and make private offers!

• Outcome: Review
• Latest audit: Sep 10, 2026 · 11:19 AM UTC
• Version: 0.2.1

Overview

The skill is mostly coherent for a human-job marketplace, but its quick-start example can immediately publish a real paid promotional job without confirmation.

Review this skill before installing or running examples. The core documentation is transparent about needing an API key and coordinating human work and payments, but do not run examples/post-job.js unless you intend to create a real public job. Use a limited MeatMarket account/API key, require human approval before posting jobs or payments, and use a low-funded dedicated or multisig wallet for any settlement flow.

A.I.G

Vulnerability Patterns

• Insecure Skill Coding Practices: Finds exploitable flaws such as hardcoded secrets or command injection
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally

Findings (1)

T09 · Insecure Skill Coding Practices

Warning

• Location: examples/post-job.js:17

Finding

Example command creates a public promotional job without explicit confirmation

Content

View full analysis

Remediation

View remediation

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Tool Misuse: Tool Parameter Abuse, Chaining Abuse, Unsafe Defaults
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands

Findings (6)

Tool Parameter Abuse

High

• Category: Tool Misuse
• Confidence: 80% confidence

Finding

The skill exposes a destructive API action (DELETE /jobs/:id) without any embedded guardrails in the skill definition such as confirmation requirements, parameter constraints, or workflow checks. In an agent context, a prompt-influenced or mistaken invocation could terminate live jobs, causing operational disruption, financial loss, or reputational damage.

Content

Scanner excerpt · SKILL.md (reported line 104)May include surrounding context.

md

| blockchain | string | yes | Base, Ethereum, Polygon, Optimism, or Arbitrum |
| time_limit_hours | number | yes | Hours to complete after acceptance |

#### DELETE /jobs/:id
Terminate a broadcasted task. Only available if status is 'open'.

#### POST /offers

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 92% confidence

Finding

The README promotes posting real-world jobs, collecting proof submissions, and settling cryptocurrency payments, but it omits any warning about privacy exposure, human-safety implications of offline tasks, or the irreversible nature of crypto transfers. For an agent-integrated skill, this can encourage autonomous use in ways that expose personal data, enable unsafe real-world tasking, or cause unrecoverable financial loss if payments are sent incorrectly or fraudulently.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium

• Category: MCP Least Privilege
• Confidence: 89% confidence

Finding

The skill documents use of environment variables and network access but does not declare any explicit tool scope or allowed-tools restrictions. In an agent platform, this increases the chance the skill can access broader capabilities than necessary, making credential exposure or unintended outbound requests more likely if the skill is invoked automatically.

Content

No source excerpt is available for this finding.

External Transmission

Medium

• Category: Data Exfiltration
• Confidence: 78% confidence

Finding

The skill instructs the agent to transmit identifying registration data and later interact with a third-party service over the network. External transmission is expected for this integration, but it still creates privacy and supply-chain risk because agent identity data and operational metadata are sent to an external platform outside the local trust boundary.

Content

Scanner excerpt · SKILL.md (reported line 41)May include surrounding context.

Register your AI entity:

bash

curl -X POST https://meatmarket.fun/api/v1/register \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[e-mail]",

Autonomous Decision Making

Medium

• Category: Excessive Agency
• Confidence: 85% confidence

Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 283)May include surrounding context.

md

// 1. Never storing your main wallet private key in a plaintext environment variable.
// 2. Using a dedicated wallet with a very small amount of funds.
// 3. Utilizing a multi-sig wallet (like Safe) where a human must approve the transaction.
// 4. Never enabling auto-approve for outgoing payments.
//
// Once the transaction is broadcast successfully using your preferred tool, 
// call the MeatMarket API to finalize the job:

Autonomous Decision Making

Medium

• Category: Excessive Agency
• Confidence: 85% confidence

Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 310)May include surrounding context.

md

1. **Use a Dedicated "Hot" Wallet:** Never connect your primary treasury or "cold" storage wallet to any automated system. Create a dedicated settlement wallet specifically for AI payouts.
2. **Limit Funding:** Only keep the minimum amount of funds (USDC, pyUSD, and ETH/MATIC for gas) required for current tasks in the settlement wallet. Top it up as needed.
3. **Never Allow Auto-Approve:** Avoid workflows where a raw private key is exposed in a plaintext environment variable for automatic signing.
4. **Use Multisig for Payments:** We strongly recommend implementing a Multisig setup (like Safe) where the agent can initiate a transaction payload, but a human must co-sign it before it is broadcast to the network.
5. **Monitor Closely:** Periodically audit the transaction history of your settlement wallet to ensure all payments align with verified proofs.

Static analysis

No suspicious patterns detected.