Skill flagged — suspicious patterns detected

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

Defi Yield

v1.3.0

DeFi 收益聚合器(Yield Aggregator)助手。帮助用户找到最佳收益策略、 分析各协议 APY、执行自动复投、追踪仓位收益。 当用户提到以下内容时激活: - "收益聚合"、"DeFi 收益"、"撸收益" - "Yearn Finance"、"Beefy Finance"、"Pendle"、"Gamm...

0· 74·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The scripts and SKILL.md largely match a DeFi yield-aggregator (queries Yearn/Beefy/Pendle/DeFi Llama and provides optimization). However, the code includes a separate billing integration (scripts/skillpay.py) that attempts to check/charge users before running logic. Billing is not documented in SKILL.md and is unrelated to the stated functionality, which is an unexpected monetization side-effect.
!
Instruction Scope
SKILL.md describes running apy_checker.py, yield_optimizer.py and a position tracker, but it does not disclose the billing flow. Both apy_checker.py and yield_optimizer.py import and immediately call billing_check at module import time (top-level), which can cause network calls and potential charges simply by running or importing the script. SKILL.md also references scripts/position_tracker.py, but no such file is present in the bundle (missing artifact).
Install Mechanism
No install spec or external downloads are used; this is an instruction-and-script bundle only. That limits disk-write/execution risk compared with arbitrary remote downloads. The code will run local Python scripts and make outbound HTTP requests to external APIs (expected for this purpose).
!
Credentials
The repository declares no required env vars, but the scripts use an environment variable SKILLPAY_USER_ID (optional) and — critically — include a hardcoded billing API key string (BILLING_API_KEY) inside scripts/skillpay.py. Embedding a live API key in code is a sensitive secret exposure and grants the code immediate ability to authenticate to an external billing endpoint. The hidden billing call before main logic is disproportionate and undocumented.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide config. It will run only when invoked. There is no installer that persists additional agents or system changes.
What to consider before installing
This skill appears to do what it says (query DeFi APY sources and suggest strategies), but it also contains an undocumented billing integration that will attempt to check/charge users via an external service before running the main logic. Notable issues: - scripts/skillpay.py contains a hardcoded API key (BILLING_API_KEY) in plaintext. That key is used to authenticate requests to https://skillpay.me and is a sensitive secret embedded in the skill. - scripts/apy_checker.py and scripts/yield_optimizer.py perform a billing_check at import time (top-level). That means simply running or importing the scripts can trigger network calls and potential billing behavior, without any mention in SKILL.md. - SKILL.md references a position_tracker.py, but that file is not included — inconsistency in the bundle. Before installing or running this skill you should: 1) Ask the publisher to explain the billing model and why billing is not documented in SKILL.md. Do not assume billing is optional. 2) Request removal of the hardcoded API key and move to a clearly-documented opt-in configuration (and only after you verify the billing provider). Never run code that contains unknown embedded credentials in an environment with sensitive secrets. 3) If you want to test, run the code in an isolated sandbox (no access to production secrets or wallets) and monitor outbound network traffic. 4) Confirm the missing position_tracker.py is provided or update SKILL.md to accurately reflect available scripts. If you are uncomfortable with undisclosed charging behavior or the embedded key, do not install or run this skill.

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

latestvk975j3a09w4smqry11nagbes7583srm8

License

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

Comments