Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Amlbot
v1.0.2AMLBot integration. Manage data, records, and automate workflows. Use when the user wants to interact with AMLBot data.
⭐ 0· 122·0 current·0 all-time
byVlad Ursul@gora050
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 (AMLBot integration) align with the runtime instructions (calls to Membrane to reach AMLBot). However the skill registry declares no required binaries while the SKILL.md requires a 'membrane' CLI to be installed and used. This is an incoherence: the skill should have declared the CLI as a required binary.
Instruction Scope
The SKILL.md stays on-topic: it instructs using the Membrane CLI to discover actions, create connections, run actions, and proxy requests to AMLBot. It does not ask the agent to read unrelated local files or environment variables, nor to transmit data to unknown endpoints beyond Membrane/AMLBot. It does instruct interactive authentication (opens a browser) and headless copying of auth codes — expected for this integration.
Install Mechanism
There is no install spec in the registry, yet the instructions tell users to install @membranehq/cli via 'npm install -g' and to use 'npx @membranehq/cli@latest' in examples. This is a moderate supply-chain risk: global npm installs and unpinned @latest usage can pull arbitrary updates. The registry should either include an explicit, pinned install spec or at least declare the required binary.
Credentials
The skill requests no environment variables or credentials and explicitly advises not to ask users for API keys, relying on Membrane to manage auth. That is proportionate for an integration that uses a proxyed authenticated connection service.
Persistence & Privilege
The skill is not always-included and is user-invocable. It does not request elevated system privileges or modify other skills' configurations. No persistence or unusual privilege is requested.
What to consider before installing
This skill appears to be a legitimate instruction-only integration for AMLBot via the Membrane platform, but it has two practical issues you should review before installing or following its steps:
- Missing declared binary: The registry metadata does not list any required binaries, but the SKILL.md expects the 'membrane' CLI. Confirm you are comfortable installing and running the Membrane CLI on your machine/environment.
- npm install / npx usage: The instructions recommend 'npm install -g @membranehq/cli' and show 'npx ...@latest'. Global npm installs and unpinned @latest usage can introduce supply-chain risk. Prefer installing into a controlled environment, pin a specific CLI version, or run via a container. Review the @membranehq/cli package (publisher, npm page, GitHub repo, release tags) before installing.
- Authentication behavior: The workflow opens a browser for OAuth-like flows and grants Membrane access to external services on your behalf. Verify what scopes/permissions the Membrane connector requests for AMLBot and ensure you're willing to delegate that access.
If you need higher assurance, ask the publisher for a registrable install spec (pinned releases) and an explicit declaration that 'membrane' is a required binary.Like a lobster shell, security has layers — review code before you run it.
latestvk972w2r7g08jpnfrbbwm1nj2398431ww
License
MIT-0
Free to use, modify, and redistribute. No attribution required.