Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Forever Moments

v1.0.0

Forever Moments social platform on LUKSO - post moments (LSP8 NFTs), mint LIKES tokens, create/join collections, and interact with decentralized social featu...

4· 614·0 current·0 all-time
byLUKSO Agent@luksoagent
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Code and SKILL.md match the described purpose: building/pinning metadata, calling Forever Moments build endpoints, preparing relays, signing digests and submitting transactions, minting LIKES, and generating images (Pollinations or DALL·E). The use of a controller private key and UP/controller addresses is expected for these on‑chain operations. However, the registry metadata (requirements section) claims 'Required env vars: none' which contradicts SKILL.md and the scripts that require FM_PRIVATE_KEY, FM_UP_ADDRESS and FM_CONTROLLER_ADDRESS.
Instruction Scope
SKILL.md and scripts are explicit about the 4-step flow (pin → build → prepare → sign → submit) and include concrete commands. The instructions require reading environment variables for private keys and calling external endpoints (forevermoments API, Pollinations, OpenAI). They also instruct the agent to sign raw digests (correct for LUKSO relays). This scope is appropriate for a wallet/controller-based minting skill, but grants the agent the ability to create on-chain transactions that spend LYX if the provided private key has permissions.
Install Mechanism
No install spec is included (instruction-only with bundled scripts). That lowers install risk: nothing will be automatically downloaded from arbitrary URLs. The repo includes local JS scripts; the README suggests installing standard npm deps (ethers, form-data) which is proportionate.
!
Credentials
The scripts require FM_PRIVATE_KEY, FM_UP_ADDRESS, and FM_CONTROLLER_ADDRESS (and optionally DALLE_API_KEY). These are proportionate to the function (signing relay digests, identifying the UP). The concern: the registry metadata lists no required env vars (incoherent with SKILL.md and code). Users may unknowingly install a skill that needs a controller private key. Additionally, the skill will sign and (if relay unavailable) directly send transactions using the provided private key — this is a sensitive capability and should only be used with a limited-permission controller key, not a full custody key.
Persistence & Privilege
always:false (default) and model invocation allowed (default). The skill does not request permanent presence or modify other skills. Autonomous invocation is permitted by platform default; that increases impact if a private key is supplied, but is not in itself unusual.
What to consider before installing
Key points before installing: - This skill requires a controller private key (FM_PRIVATE_KEY) and Universal Profile addresses — supplying that key gives the skill ability to sign and submit on-chain transactions that can spend LYX. Only use a key with minimal permissions (a controller with LIMITED KeyManager permissions, e.g., restricted to the specific actions you trust), never your main custody key. - The registry metadata incorrectly states no required env vars while SKILL.md and scripts require FM_PRIVATE_KEY, FM_UP_ADDRESS and FM_CONTROLLER_ADDRESS; treat the SKILL.md as authoritative and double-check environment variables before use. - The scripts may fall back to direct execution (paying gas from the controller) if relayer quota is exhausted; that behavior is explicit in code but important to understand because it causes real LYX spending. - There is a hardcoded fallback KeyManager address in post-moment-ai.js used when relayPrepare does not return a keyManagerAddress — verify that address and why it is used before trusting the code. - Image generation uses Pollinations (free) or OpenAI DALL·E (requires DALLE_API_KEY and incurs cost). Confirm you want the agent to call those external services and be billed for them if using DALL·E. - Recommended mitigations: test on a LUKSO testnet or a disposable controller key; review the scripts locally; run with read-only/sample environment values first; avoid giving high-privilege private keys to the agent; inspect and, if necessary, remove or change the hardcoded keyManager fallback.

Like a lobster shell, security has layers — review code before you run it.

latestvk9770t8neqjz49gh36jmkxg13181fnj9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📸 Clawdis

Comments