Security checks for vulnerabilities and agentic risk
Overview
This skill is a disclosed Botcoin game integration, but users should treat its public social verification, wallet signing, payments, and on-chain claims carefully.
Before installing or using this skill, be comfortable posting a public X verification message tied to the wallet fingerprint, managing a local secret key, signing transactions, and making irreversible payment or on-chain actions. Use pinned dependency versions where possible, keep the secret key out of logs and shared files, and manually verify addresses, coin IDs, invoices, and burn transactions before submitting them.
## Dependencies
This skill requires the `tweetnacl` and `tweetnacl-util` npm packages for Ed25519 cryptography.
```bash
npm install tweetnacl tweetnacl-util
text
### Technical Analysis
The documented installation command resolves mutable package versions from the npm registry. The project provides neither exact reviewed versions nor a lockfile with integrity information. Consequently, separate installations may retrieve different dependency versions.
These packages operate directly on Ed25519 private-key material and transaction signatures. If a package, transitive dependency, maintainer account, or registry delivery path were compromised, attacker-controlled code could run in the same environment as the generated wallet secret key. A malicious update could capture key material, alter destination addresses or transaction fields before signing, or forge misleading signing behavior.
The audit found no evidence that the currently named packages are malicious. The vulnerability is the unsafe, non-reproducible dependency acquisition process documented by the Skill.
### Attack Path
1. An attacker compromises a dependency release channel, maintainer account, or relevant package version.
2. The victim follows the documented `npm install tweetnacl tweetnacl-util` command.
3. npm resolves and installs the compromised mutable version.
4. Malicious installation or runtime code executes in the wallet-signing environment.
5. When the Skill generates or uses an Ed25519 keypair, the dependency accesses the secret key or modifies data passed for signing.
6. The attacker can exfiltrate key material through a network channel or cause the victim to authorize manipulated game transactions.
### Impact Assessment
Successful exploitation would provide code execution with the privileges of the
...[truncated 516 chars]
Remediation
View remediation
Remediation Suggestions
Pin each dependency to a reviewed exact version rather than allowing npm to resolve the latest release:
json
The skill requires users to post a public X/Twitter verification message tied to their wallet fingerprint, but it does not foreground this as a privacy and identity-linkage risk before the flow begins. That can cause users to unintentionally deanonymize a wallet, create a durable public association between social identity and wallet activity, and expose themselves to tracking or targeting.
Content
No source excerpt is available for this finding.
Missing User Warnings
Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding
The withdrawal section describes permanent on-chain minting and one-time withdrawal semantics, but it does not present this as a prominent irreversible-action warning. Users may not appreciate that linking the wrong Base address or claiming prematurely can result in irreversible token delivery and permanent state changes that cannot be undone.