Guardivia

Outcome-led solution

SIM-Box Detection

SIM boxes and SIM farms are banks of SIM cards used to terminate commercial SMS (or calls) as if they were ordinary subscriber traffic, bypassing interconnect and A2P termination charges.

The challenge

  • SIM-box traffic resembles genuine P2P
  • Ranges rotate to evade static blacklists
  • Bypass indicators are only visible at the receiving handset

How does Guardivia detect SIM boxes?

Guardivia detects SIM-box and SIM-farm termination by profiling MSISDN behaviour in the SMS Signaling and ESME Gateway Firewall, including submission velocity, fan-out, content commerciality, geographic pattern and history, and by confirming at real handsets through Honeypot SMS Testing that test messages arrive from local subscriber numbers instead of the submitted sender ID.

Last reviewed 2026-09-12 by the Guardivia QoS Engineering Team. Product facts on this page describe current capabilities; items marked “where supported”, “optional”, “integration” or “consultancy” are confirmed per deployment.

Solution flow

Derived from this solution
  1. 01
    Behavioural profilingMSISDN velocity, fan-out and content analysis with AI-assisted scoring under human governance.
  2. 02
    Handset confirmationSuspected SIM-box termination verdicts from device evidence.
The complete approach and product responsibilities remain listed below.

Approach

How Guardivia addresses it

  1. 01

    Behavioural profiling

    MSISDN velocity, fan-out and content analysis with AI-assisted scoring under human governance.

    Guardivia SMS Signaling and ESME Gateway Firewall →
  2. 02

    Handset confirmation

    Suspected SIM-box termination verdicts from device evidence.

    Guardivia Honeypot SMS Testing and Route Assurance →

Outcomes

  • SIM-box ranges identified and actioned
  • Evidence for commercial and regulatory follow-up

Products involved

FAQ

Questions about this solution

Does detection block subscribers automatically?

No. AI proposes classifications and an authorised engineer confirms enforcement; policy can quarantine or tag before blocking.

See it running on your traffic profile.

Talk to the engineers who build the platform. Demos use your protocols, your integration points and your policy questions.