knowbster

WarnAudited by ClawScan on May 10, 2026.

Overview

The skill matches its crypto marketplace purpose, but it can use a raw wallet private key to make on-chain purchases without clear spend limits or approval controls.

Review carefully before installing. If you use it, connect only a dedicated low-balance wallet, require manual approval for purchases/listings/validations, set explicit spend limits, and do not upload private or secret content to IPFS.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If an agent or script uses a funded wallet key, it may be able to authorize transactions from that wallet.

Why it was flagged

The skill initializes a blockchain client from a raw private key, giving it wallet signing authority. The registry metadata declares no primary credential or required environment variable.

Skill content
const client = new KnowbsterClient(process.env.PRIVATE_KEY);
Recommendation

Use only a dedicated low-balance wallet, declare the credential requirement clearly, and require explicit user approval for every transaction.

What this means

A mistaken or manipulated token selection could cause the agent to spend ETH irreversibly.

Why it was flagged

The purchase method sends a payable on-chain transaction for the price returned by the contract, without an evident max price, budget check, allowlist, or user confirmation gate.

Skill content
const tx = await this.contract.purchaseKnowledge(tokenId, { value: knowledge.price, gasLimit: 300000 });
Recommendation

Add hard spend limits, display price and gas before signing, require per-purchase confirmation, and avoid autonomous purchases unless the user has set a clear budget.

What this means

Knowledge content uploaded for sale may leave the local environment and may be hard to remove once published through IPFS-related workflows.

Why it was flagged

The documented listing workflow sends selected knowledge content and a Pinata bearer token to an external IPFS pinning provider. This is purpose-aligned, but users should understand the data boundary.

Skill content
fetch('https://api.pinata.cloud/pinning/pinJSONToIPFS', ... 'Authorization': `Bearer ${process.env.PINATA_JWT}` ... content: content)
Recommendation

Upload only content intended for marketplace publication, use a scoped Pinata token, and avoid including secrets or private user data.

What this means

Future installs could resolve to newer dependency versions than the ones originally tested.

Why it was flagged

The package depends on external npm libraries using semver ranges. This is normal for the stated purpose, but the provided artifacts do not include a lockfile.

Skill content
"dependencies": { "ethers": "^6.9.0", "axios": "^1.6.0" }
Recommendation

Install from a trusted source and prefer a lockfile or pinned dependency versions for production use.