Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
forgex
v1.0.0Manage wallets, launch tokens, and perform on-chain market making on Solana via a simple CLI without programming, supporting batch trades and workflow automa...
⭐ 0· 52·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (wallets, token launches, on‑chain market making on Solana) matches the SKILL.md commands (wallet create/import/export, token create, transfer, volume bot, RPC config etc.). The requested operations are what you'd expect for such a CLI.
Instruction Scope
The instructions ask users to import and export private keys, pass passwords and private keys directly on the command line (e.g. --password "your-password", --private-key "Base58Key..."), and write backups to local files (CSV/JSON). Passing secrets on the command line exposes them to process lists and shell history; exporting unencrypted CSVs or using insecure file paths risks accidental disclosure. The SKILL.md also instructs storing API keys/config via `forgex config set` (codexApiKey) but the skill metadata doesn't declare this stored secret. While these actions are within the functional scope, the instructions are insecure and under-specified about where/how secrets are stored or protected.
Install Mechanism
The skill itself has no install spec in the registry (instruction-only), but SKILL.md instructs users to run `npm install -g forgex-cli`. Installing a third-party npm CLI is a common pattern but carries supply-chain risk: the package source/homepage is not provided in registry metadata, and the registry entry lacks provenance (no homepage, unknown source). This is a moderate risk that warrants verifying the npm package and upstream repository before installing.
Credentials
Registry metadata declares no required env vars or primary credential, yet the SKILL.md instructs adding a Codex API key via `forgex config set codexApiKey` and setting RPC endpoints—both effectively become stored credentials/config. The skill also demonstrates handling of many sensitive artifacts (private keys, backups, passwords) without describing secure storage. The absence of declared required env vars/config in metadata is a mismatch with the SKILL.md's behavior.
Persistence & Privilege
The skill is not marked always:true and does not request elevated platform privileges. Autonomous invocation is allowed by default (platform behavior) but there is no metadata indicating permanent agent-wide changes or modifications to other skills. This dimension does not raise additional red flags on its own.
What to consider before installing
Do not install or run this CLI without checking provenance: verify the npm package (forgex-cli) and its upstream repository (GitHub) and confirm the publisher identity. Avoid passing passwords or private keys on the command line (they appear in process lists and shell history); prefer using prompting, secure local keystores, or hardware wallets. Inspect how and where the CLI stores keys/config (unencrypted CSV or JSON backups are risky). If you must test, use throwaway wallets and a devnet/testnet RPC endpoint, and run with --dry-run first. If you are not comfortable auditing an npm package, do not install it. Finally, note the registry metadata lacks a homepage/source and the slug differs from the skill name (fogex vs forgex) — that mismatch is another reason to verify origin before trusting it with real funds.Like a lobster shell, security has layers — review code before you run it.
latestvk97ftd59wzj5f9qjs5t123rzks83g7mn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.