Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Order & Returns Manager
v1.0.0Manage UK-compliant Shopify and WooCommerce orders via chat, including status, returns, refunds, exchanges, edits, fraud flags, lost parcels, and reports.
⭐ 0· 51·0 current·0 all-time
byHussain Khuzema@hussainpatan9
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's functionality (manage Shopify and WooCommerce orders, returns, refunds, fulfilments) legitimately requires store API credentials and the Shopify admin scopes the CONFIG.md lists. However the registry metadata declares no required environment variables or primary credential — that contradicts the SKILL.md which instructs the agent to ask for and store SHOPIFY_ACCESS_TOKEN / WC_CONSUMER_KEY / WC_CONSUMER_SECRET. This metadata/instruction mismatch is an incoherence that should be resolved.
Instruction Scope
SKILL.md is detailed and stays within the stated purpose: it prescribes REST calls to Shopify and WooCommerce, carrier web_fetch fallbacks, and UK-law checks. It instructs the agent to ask the user for API tokens and to store them under orders_config in memory. The instructions do not require unrelated files or credentials, but they do not specify secure storage, retention policy, or where memory persists — leaving sensitive tokens potentially stored long-term without safeguards.
Install Mechanism
This is instruction-only (no install spec, no code files to execute). That reduces surface area because nothing is downloaded or written by an installer. The skill relies on runtime network calls and agent memory rather than installing binaries.
Credentials
The set of secrets the skill needs (Shopify access token and WooCommerce consumer key/secret) is proportionate to the feature set. The concern is that the published registry metadata lists NO required credentials while the runtime instructions explicitly request sensitive API tokens. Also the skill asks to store these tokens in agent memory but gives no guidance about encryption, access controls, or retention — which is a material omission for secrets.
Persistence & Privilege
The skill is not 'always' enabled and does not request elevated system privileges. However it does instruct the agent to 'ask once and store' API tokens and other config in memory (orders_config) — this implies persistent storage in the agent's memory store. Confirm whether that memory is encrypted, who can read it, and how to revoke tokens; absence of that detail is a privacy/security risk but not proof of malicious intent.
What to consider before installing
This skill appears to do what it says (managing orders on Shopify/WooCommerce), but the published metadata inaccurately claims 'no credentials required' while the instructions require you to supply store API tokens and to let the bot store them. Before installing or using it:
- Treat the required API tokens as highly sensitive. Create a dedicated custom app or API key pair with the minimum necessary scopes (least privilege) rather than using an owner/admin token. Limit write scopes where possible and rotate/revoke keys after testing.
- Ask the skill/vendor (or the platform) where the tokens are stored: is the agent memory encrypted at rest, who can access it, and how long are keys retained? Confirm a way to delete or revoke stored credentials.
- Don’t paste tokens into public channels. Prefer to enter them via a secure settings UI if available.
- If you cannot verify secure storage or origin of the skill (source is unknown, no homepage), consider rejecting it or testing first with a low-privilege test store account and test tokens.
- If you decide to proceed in production, limit liability by using an account with only the necessary Shopify/WooCommerce scopes and by monitoring access and token usage for anomalous activity.
If the publisher can (a) update the registry metadata to declare required credentials, and (b) document how secrets are stored/secured and how to revoke them, that would materially reduce the concern.Like a lobster shell, security has layers — review code before you run it.
ecommercevk978ayzkq7eb0nxy0rbam9ptvs84mwwtfraudvk978ayzkq7eb0nxy0rbam9ptvs84mwwtfulfilmentvk978ayzkq7eb0nxy0rbam9ptvs84mwwtlatestvk978ayzkq7eb0nxy0rbam9ptvs84mwwtordersvk978ayzkq7eb0nxy0rbam9ptvs84mwwtrefundsvk978ayzkq7eb0nxy0rbam9ptvs84mwwtreturnsvk978ayzkq7eb0nxy0rbam9ptvs84mwwtshopifyvk978ayzkq7eb0nxy0rbam9ptvs84mwwtukvk978ayzkq7eb0nxy0rbam9ptvs84mwwtwoocommercevk978ayzkq7eb0nxy0rbam9ptvs84mwwt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.