Skip to content

Cryptocurrency wallet operations

A tool parameter contains a recognized wallet command or wallet API name.

An agent may create or manipulate keys that control funds. Unexpected wallet activity can also be a precursor to theft or an attempt to create a destination for stolen funds.

An agent working on a non-financial application invokes wallet generation during an unrelated setup step.

This is a fictional example, not an event from a customer.

The rule scans parameters for selected wallet CLI names and API method names. Some matches concern account enumeration or key import rather than creation.

Rule IDEvent categoryTierBase severity
RULE_WALLET_CLI_DETECTEDwallet_generationCommunityHIGH

Base severity is the rule default. A finding involving content saved for later execution may have a lower severity. Your loaded rule version and event details determine the finding you see.

Confirm the task requires wallet work and distinguish development wallets from wallets holding real assets. Keep custody decisions and production key handling under appropriate control.

Approved blockchain development, wallet tests, and documentation mentioning a supported command can match.

Unlisted wallet tools, custom key generation, or operations hidden inside a program can be missed.

The wallet_generation category is broader than literal generation. This rule does not show that a new key was created, that funds were transferred, or that a wallet belongs to an attacker.

A finding describes a pattern in captured activity. Review the original call, its result, and the task context before concluding that harm occurred. Absence of a finding does not establish that an operation is safe.

Browse this category. Find a rule by ID.