Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AliasKit
v1.0.0Persistent digital identity for this agent. Provides real email, phone number, virtual payment card, and TOTP codes. Use this skill whenever the agent needs:...
⭐ 0· 37·0 current·0 all-time
byNalin@nalin-atmakur
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
medium confidencePurpose & Capability
The described functionality (email, phone, virtual card, TOTP, realtime messages) matches the SDK methods and scripts included: the skill uses an AliasKit SDK to create/list identities, receive emails/SMS, register TOTP, and reveal virtual card data. Requiring an API key and client-side card encryption is coherent with the stated purpose.
Instruction Scope
The runtime instructions and scripts instruct the agent/user to: run scripts/setup.sh, provide or paste an ALIASKIT_API_KEY, run npm install aliaskit@latest, and (on card setup) collect full card details and CVC. identity.json persisted next to SKILL.md will contain the API key, identityId, and cardKey. These actions collect and persist highly sensitive data and grant the skill access to mail/SMS contents and payment reveal operations. The SKILL.md stays within the AliasKit domain (no unexpected external endpoints), but it directs broad data collection and local storage of secrets without describing encryption/protection beyond a generated cardKey.
Install Mechanism
There is no registry install spec, but setup.sh runs npm install aliaskit@latest when invoked. Installing the latest npm package at runtime is a moderate supply-chain risk (expected for SDK usage) — the script does not pin a version and fetches directly from the registry.
Credentials
Registry metadata declares no required env vars, yet setup.sh and the SDK logic rely on ALIASKIT_API_KEY (and the code persists that key into identity.json). The skill also requests collection of full card details and stores a generated cardKey in identity.json. Requiring and persisting these credentials is functional for the service, but the mismatch between declared requirements and actual behavior and the plaintext storage of secrets are notable concerns.
Persistence & Privilege
always:false and normal user-invocation are set. The skill does not request to be always-enabled and does not modify other skills or system-wide configuration. Its persistence is limited to writing identity.json in the skill directory and optionally installing an npm package when setup.sh is run.
What to consider before installing
Before using this skill, consider the following:
- This skill requires an AliasKit API key though the registry metadata doesn't declare it — you will be prompted to provide or paste ALIASKIT_API_KEY during setup.sh. Treat that key as sensitive.
- setup.sh will install aliaskit@latest via npm at runtime (un-pinned). If you trust this vendor, pin a known-good version or review the package before installing.
- identity.json stores sensitive values (apiKey, cardKey, identityId) in the skill directory in plaintext. Decide where that file will live and restrict filesystem permissions; do not commit it to version control.
- The skill explicitly guides you to enter real card details (number, CVC, expiry, cardholder name). Only provide such data if you trust the AliasKit service and understand how the card is used and billed. Prefer using a low-privilege/test card if possible.
- Verify the AliasKit service and the aliaskit npm package (source repo, integrity, organization) before providing credentials or payment details. Review network endpoints (baseUrl defaults to https://www.aliaskit.com/api/v1) and privacy/security docs on the vendor site.
- If you need stronger guarantees, request the publisher to: declare required env vars in metadata, pin SDK versions, and describe how identity.json is protected (encryption at rest or advice to store in a secure secret store).
Given the sensitive data involved and the metadata mismatch, proceed only after you confirm vendor trust and storage protections.scripts/setup.sh:59
Environment variable access combined with network send.
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97bw3psw2mvtj5m0ecyh4jwwn84sgnx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.