Multi Platform Synergy

• Outcome: Review
• Latest audit: Sep 16, 2026 · 9:56 AM UTC
• Version: 1.0.0

Overview

This skill is transparent about coordinating multi-account social posting, but it directs reciprocal engagement across public platforms without clear compliance, consent, or anti-manipulation boundaries.

Install only if you control or are authorized to use the involved accounts, will follow each platform's rules, and will avoid undisclosed engagement inflation or simulated independent discussion. Review or clear memory/cycle-state.json if campaign topics, post IDs, or account mappings should not persist locally.

A.I.G

Vulnerability Patterns

• 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
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

Findings (1)

other

Warning

• Location: SKILL.md:43

Finding

Coordinated Inauthentic Engagement Across Controlled Platform Accounts

Content

View full analysis

Vulnerability Details

File Location: SKILL.md:43-47
Vulnerability Type: other: Coordinated inauthentic engagement
Risk Level: Medium

Evidence

markdown

### 2. Cross-account promotion

After publishing, comment on each other's posts to form a discussion chain:
- Each post must receive at least one substantive comment from another team member.
- Comments must include a specific data reference or an additional viewpoint.

The excerpt above is an English translation of the original documentation.

Technical Analysis

The Skill explicitly directs a group of coordinated accounts to comment on one another's posts and requires every post to receive engagement from another team member. This creates engagement that may appear independent or organic even though it is generated by commonly coordinated participants.

Requiring concrete data or additional viewpoints may improve comment quality, but it does not mitigate the underlying concern: the interactions are mandatory components of an account-coordination strategy rather than independently initiated engagement. This behavior can manipulate perceived popularity, discussion activity, and platform ranking signals.

No executable automation, credentials, platform API implementation, or privilege-escalation mechanism was present in the audited project. The risk arises from the operational instructions themselves.

Attack Path

1. An operator loads the Skill and controls or coordinates accounts on the supported platforms.
2. The accounts publish related posts under a shared topic.
3. After publication, the operator follows the mandatory reciprocal-commenting instruction.
4. Each post receives a substantive comment from another coordinated participant.
5. Users and platform ranking systems may interpret the resulting discussion chain as independent engagement.
6. Repetition across multiple posts or platforms can amplify misleading popularity and interaction signals.

Impact Assessme

...[truncated 662 chars]

Remediation

View remediation

Remediation Suggestions

1. Remove the requirement that every post receive a comment from another coordinated account.
2. Prohibit reciprocal engagement whose primary purpose is to inflate interaction or ranking signals.
3. Permit cross-account comments only when they are independently useful, contextually necessary, and compliant with the relevant platform's policies.
4. Disclose shared ownership, organizational affiliation, or coordinated control where users could otherwise interpret the accounts as independent.
5. Add explicit safeguards forbidding fabricated personas, deceptive discussion chains, engagement manipulation, and undisclosed automation.
6. Introduce a platform-policy review checkpoint before publishing or interacting.
7. Record the business justification and approving operator for coordinated interactions so questionable campaigns can be reviewed.
8. Prefer transparent links, labeled collaborations, or official organization accounts over simulated peer discussion.
9. Implement rate limits and human approval for any automated cross-account engagement.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (2)

Missing User Warnings

Medium

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

Finding

The skill explicitly coordinates multi-account posting, cross-commenting, cross-referencing, and metric collection across several external platforms, but it does not warn the user that this behavior may violate platform anti-spam, anti-manipulation, or account policy rules. In this context, the omission is material because the workflow is designed to simulate organic engagement and can expose users to account enforcement, reputational harm, or misuse of collected platform data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low

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

Finding

The skill stores persistent operational state in a local JSON file but does not disclose this behavior or describe what data may be retained. Even if the stored fields look operational, persistent local state can expose campaign details, posting history, account mappings, or future content plans to other local users, logs, backups, or downstream tooling.

Content

No source excerpt is available for this finding.