Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Ewebinar
v1.0.0EWebinar integration. Manage Webinars, Integrations, Users. Use when the user wants to interact with EWebinar data.
⭐ 0· 56·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill claims to integrate with EWebinar via Membrane (reasonable), but the SKILL metadata lists no required binaries or config paths while the instructions explicitly require running `npx @membranehq/cli@latest` and creating credentials at `~/.membrane/credentials.json`. Those runtime requirements are expected for this purpose but were not declared in the manifest, which is an incoherence.
Instruction Scope
The SKILL.md tells the agent to run the Membrane CLI, open browser auth flows, and read/write credentials in the user's home directory. It also documents a proxy feature that will forward arbitrary full URLs through Membrane. These behaviors are sensible for a connector but broaden scope (writes persistent credentials and can issue arbitrary proxied requests) and should have been explicitly declared.
Install Mechanism
There is no install spec (instruction-only), but the skill relies on `npx @membranehq/cli@latest`. That causes dynamic package download/execution when first invoked — a normal pattern for CLI usage but higher-risk than a purely declared/bundled dependency because code is fetched from npm at runtime.
Credentials
The manifest lists no required env vars or config paths, yet the instructions rely on a Membrane account and store credentials at `~/.membrane/credentials.json`. Not declaring the config path or the need for a Membrane account/credentials is a mismatch and hides the fact the skill will create persistent credentials on the host.
Persistence & Privilege
The skill does not request 'always' or other elevated platform privileges, but it instructs creating/storing credentials under the user's home (`~/.membrane/credentials.json`). Persisting its own auth state is normal for a connector, but the manifest should declare that behavior so users know files will be created.
What to consider before installing
This skill appears to be a legitimate Membrane-based EWebinar connector, but there are important omissions and a few risks to consider before installing:
- Manifest mismatches: The runtime instructions require `npx` and will create `~/.membrane/credentials.json`, yet the skill's manifest declares no required binaries or config paths. Ask the author to update the manifest to list required binaries (npx/npm/node) and the config path so you know what will be touched.
- Dynamic install risk: Running `npx @membranehq/cli@latest` will download and execute code from npm the first time — verify the package identity (publisher, repo) before allowing it, or run in an isolated environment.
- Persistent credentials: The login flow stores credentials locally. Review what the Membrane CLI stores in `~/.membrane/credentials.json` and whether those credentials grant access beyond EWebinar. If you cannot inspect the stored file or do not trust the package, avoid running the login flow on sensitive systems.
- Proxy capability: The skill documents that Membrane can proxy arbitrary URLs. That is convenient but can be used to send requests to unintended endpoints. Confirm that the agent using this skill will only be asked to call EWebinar endpoints and not arbitrary external services, or constrain the Membrane connection accordingly.
Recommended actions before use: request an updated manifest that declares required binaries and config paths; verify the `@membranehq/cli` npm package and its repository; test the login flow in a throwaway account or isolated VM; and confirm what domains and scopes the Membrane connection will permit.Like a lobster shell, security has layers — review code before you run it.
latestvk97f86s2qqmnh5vjz66pgq8y5h84cjxe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
