Skill flagged — suspicious patterns detected

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

Levity

v1.0.0

Levity integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Levity data.

0· 87·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name and description (Levity integration) match the instructions: it uses Membrane to discover and run Levity-related actions and proxy API calls. Using a connector/proxy to access Levity is coherent with the stated purpose.
!
Instruction Scope
SKILL.md explicitly instructs running npx @membranehq/cli and browser-based login, creating/reading ~/.membrane/credentials.json, listing connections, running actions, and proxying arbitrary API requests through Membrane. These instructions go beyond simple read-only queries (they create local credentials and can proxy arbitrary requests), so they should have been reflected in the metadata and clearly disclosed to users.
Install Mechanism
No install spec is present (instruction-only), but the instructions rely on npx which will fetch and execute the @membranehq/cli package from the npm registry at runtime. Executing remote packages via npx is normal but introduces moderate risk because arbitrary code from the npm registry will run and may write files (e.g., credentials) locally.
!
Credentials
The registry metadata lists no required config paths or credentials, yet the instructions state that credentials will be stored at ~/.membrane/credentials.json and that a Membrane account is required. This mismatch (undeclared config path and implicit third-party account) is a proportionality and transparency issue. No environment variables are requested, which is consistent with the recommendation to use Membrane instead of asking for API keys.
Persistence & Privilege
The skill does not request always:true or other elevated persistent privileges. It does direct the user to create a connection and store credentials in the user's home (~/.membrane), which is normal for CLI-based auth flows but should be noted.
What to consider before installing
This skill appears to do what it claims (manage Levity via Membrane), but there are a few things to weigh before installing/running it: - npx executes code fetched from the npm registry. If you run the commands the skill suggests, you're executing @membranehq/cli code on your machine — consider verifying the package (publisher, npm package page, checksum) first. - The Membrane CLI will create and use a credentials file at ~/.membrane/credentials.json (the SKILL.md mentions this), but the skill metadata did not declare any config paths. Expect credentials and proxied request data to be handled by Membrane; if your Levity data is sensitive, confirm Membrane's privacy/security posture and where data is routed/stored. - The proxy feature lets you send arbitrary requests through Membrane. Be cautious about sending secrets or sensitive payloads through a third-party proxy. - If you want to reduce risk, inspect the CLI package before running (npm view @membranehq/cli, download the tarball and audit contents), or prefer using Levity's official API directly if you control credentials and want to avoid a third-party proxy. If you proceed, ensure you understand and trust the Membrane service and the @membranehq/cli package, and check the ~/.membrane credentials file after login so you know what was stored.

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

latestvk973x1d9pvkq734gcj4zn4w5e184h1tw

License

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

Comments