Dormant account activity rule

A dormant account activity rule detects sudden activity on an account that has had no customer-initiated transactions for a defined period. Dormant accounts are attractive to fraudsters because their owners are not watching them, so the first transaction after a long silence is worth a closer look.

The fraud scenario this rule addresses

An account with no recent activity is rarely checked by its owner, so a fraudster who obtains its credentials, or a mule recruiter who buys access to it, can use it with little chance of the genuine customer noticing. The pattern is a long silence followed by an abrupt run of incoming and outgoing transfers.

Dormant accounts are also used to receive and pass on stolen funds, because an account with a long clean history draws less suspicion than a freshly opened one.

Data the rule requires

Example logic

Illustrative pseudocode: it compares each event with the rule's parameters and flags the ones that match. Parameters are symbolic: every value is institution-specific and has to be derived from your own transaction distribution.

RULE dormant_account_activity
  FOR EACH event E on account A:
    last = max(timestamp) of customer-initiated transactions on A
    idle = E.timestamp - last
    IF idle >= :dormancy_period
       AND E.is_customer_initiated
       AND (E.amount >= :min_amount OR E.type IN :risky_types):
      RAISE alert(rule = "dormant_account_activity",
                  account = A, evidence = E)

Choosing a threshold

The central parameter is the dormancy period, and it trades coverage against noise. A short period catches accounts that are merely infrequently used, such as an annual-bills account, and floods the queue. A long period leaves a large population of quiet accounts uncovered, and attackers who need only a few weeks of silence slip through.

The second parameter is what counts as activity. If interest postings, fees or incoming credits reset the dormancy clock, almost no account is ever dormant, so the rule must count only customer-initiated actions. Whether an incoming credit should break dormancy is a real design question, because incoming funds from an unknown sender are exactly what a mule account receives.

A minimum amount or risky transaction type keeps the rule from alerting on trivial first transactions, but a floor that is too high lets an attacker test the account with small amounts first.

False positives to expect

Many accounts are legitimately quiet and then used: a seasonal worker returning to a country, a student account reactivated for term, someone holding an emergency savings account, a migrant worker's account used only on trips home, or a customer who has had no need for a product until a major purchase.

Product type matters: an account designed for occasional use, such as a savings pot or an annual-subscription account, will trip the rule routinely. Segmenting by product and using the account's own historical gaps, rather than one fixed dormancy period for everyone, reduces this considerably.

Investigating an alert from this rule

  1. Establish the account's history: when it was opened, how it was used, and how long it has been idle.
  2. Look at the first reactivation event: its type, amount, channel and device.
  3. Check for changes to contact details, credentials or linked devices in the lead-up to reactivation.
  4. Look at the sources of incoming money and the destinations of outgoing money, and how quickly funds leave after arriving.
  5. Check whether the account owner can be reached by a contact detail that predates the reactivation, and confirm the activity with them.
  6. If the account looks taken over or used as a pass-through, tag it so subsequent activity is judged in that light.

Related rules

Where this rule fits

The use case this rule supports is covered in unusual transaction behaviour, and the fraud rules engine page describes how conditions like these are expressed and versioned.

Common questions

What is a dormant account activity rule?

A dormant account activity rule is a fraud rule that raises an alert when an account with no customer-initiated transactions for a defined period suddenly becomes active. Dormant accounts are attractive targets because their owners rarely check them, and they are also used to pass on stolen funds because a long clean history attracts less suspicion.

The key design choice is what counts as activity. Interest, fees and incoming credits should not reset the dormancy clock, otherwise almost no account ever qualifies as dormant.

Many legitimate accounts are quiet and then used, for example seasonal accounts, savings pots and accounts held for emergencies, so the rule normally compares the new activity with the account's own history of gaps rather than applying a single period to everyone.

Discuss your transaction monitoring requirements

Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.

Request a demo