T06 · System Persistence
- Location
SKILL.md:352- Finding
Root-Level Persistent Execution Through a System-Wide Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The basic FANZA query skill is disclosed, but the optional bot setup asks users to run mutable external code persistently, including as root with messaging tokens.
Use the on-demand curl examples only if you are comfortable querying an unofficial adult-content FANZA endpoint. Treat the Discord/Telegram bot section as a separate unreviewed application: do not run it as root, do not enable a systemd service without a dedicated locked-down user, avoid putting tokens in command URLs or committed config files, and pin/review the cloned code and dependencies before starting it.
SKILL.md:352Root-Level Persistent Execution Through a System-Wide Service
SKILL.md:280Unpinned Remote Application and Dependency Retrieval Followed by Execution
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.
1. Create app at [discord.com/developers](https://discord.com/developers/applications) → **Bot** tab → **Add Bot** → copy Token
2. **OAuth2** → **URL Generator** → scopes: `bot` → permissions: `Send Messages`, `Embed Links` → invite bot
3. Right-click server → **Copy Server ID** (enable Developer Mode first)
4. Right-click channel → **Copy Channel ID**
### Telegram Setup (Optional)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
---
name: avbuzz
description: Query AV new releases, rankings, and actress info from FANZA GraphQL API. No authentication required. Supports direct curl queries and optional Discord/Telegram bot deployment.
version: 1.1.0
user-invocable: true
metadata:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## API Overview
**Endpoint:** `POST https://api.video.dmm.co.jp/graphql`
**Authentication:** None (public API)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Search by actress name, title, video code, or any keyword:
curl -s -X POST https://api.video.dmm.co.jp/graphql \
-H "Content-Type: application/json" \
-d '{"query":"{ legacySearchPPV(limit: 10, offset: 0, sort: SALES_RANK_SCORE, floor: AV, queryWord: \"蒼井空\") { result { contents { id title deliveryStartAt contentType maker { name } actresses { id name } packageImage { largeUrl } review { average count } bookmarkCount } pageInfo { totalCount } } } }"}'
The skill is presented as a simple unauthenticated query tool, but it also includes instructions for deploying a persistent Discord/Telegram bot with scheduled notifications and tracking. That expands the trust boundary from on-demand local API calls to long-running external integrations that can continuously transmit content and metadata, which is materially different from the stated scope.
The documentation says the skill only supports on-demand queries and cannot autonomously push notifications, then immediately directs users to deploy a bot that performs scheduled digests and alerts. This contradiction can mislead reviewers and users about autonomy, persistence, and external transmission behavior.
The instructions tell users to place Discord and Telegram bot tokens directly into a local config file without emphasizing credential sensitivity, storage hygiene, or access controls. Exposed bot tokens can allow unauthorized control of messaging integrations, message exfiltration, impersonation, or spam from the victim's accounts.
The Telegram setup instructs users to place a bot token directly into a URL when calling getUpdates. Tokens embedded in shell history, browser history, logs, screenshots, or shared terminals are easily leaked and can grant full bot control to an attacker.
### Telegram Setup (Optional)
1. Message `@BotFather` on Telegram → `/newbot` → copy Token
2. Send a message, then visit `https://api.telegram.org/bot<TOKEN>/getUpdates` → find `chat.id`
3. Leave both fields empty to run Discord-only
### Discord Slash Commands
VPS and systemd deployment steps introduce remote administration and persistent-service behavior that are unnecessary for a local query skill. This can normalize running a long-lived networked process as root on a server, increasing operational and security risk beyond the skill's advertised purpose.
The systemctl enable guidance explicitly configures the service to persist and auto-start, turning a simple skill-adjacent utility into a long-running background process. Persistence increases exposure to secret leakage, unintended ongoing external communication, and abuse if the deployed bot or host is compromised.
```bash
systemctl daemon-reload && systemctl enable avbuzz && systemctl start avbuzz
journalctl -u avbuzz -f # View logs
The manifest requests both shell execution and the curl binary for a skill whose stated purpose is simple querying of a public GraphQL API. Granting exec enables arbitrary command execution beyond the minimum needed for the advertised functionality, which increases the blast radius if the skill content, parameters, or downstream prompts are manipulated into constructing unsafe shell commands.
No suspicious patterns detected.