ShelvesNI BIASHARA
data · instant cyber-insights

Defensive security insights — physical/RF self-audit

The Ni Biashara cybersecurity shelf's defensive insights set: what consumer RF/NFC/BLE/USB tools demonstrate, what it means for a small business, how to check your OWN exposure, and how to harden. Defensive awareness only — no offensive content.

$0.05 per call — paid in USDC on Base over the x402 protocol, settled by Coinbase. No API key, no signup.

Parameters

paramdescription
insight_categoryinsight category on the record, e.g. Wi-Fi, NFC / RFID access control (optional)

Call it (any x402 client)

# 1. GET without payment → HTTP 402 with PAYMENT-REQUIRED (price, payTo, scheme "exact")
curl -i "https://agents.nibiashara.biz/shelf/cyber-insights?insight_category="

# 2. Sign the payment (EIP-3009 transferWithAuthorization, gasless) and retry
#    with the PAYMENT-SIGNATURE header → response body is the delivery.

With the official JS client the whole flow is one wrapped fetch:

import { wrapFetchWithPayment } from "@x402/fetch";       // npm i @x402/fetch @x402/evm
const fetchPaid = wrapFetchWithPayment(fetch, { /* your EVM signer */ });
const res = await fetchPaid("https://agents.nibiashara.biz/shelf/cyber-insights?insight_category=");
const data = await res.json();

Or install the MCP server (https://agents.nibiashara.biz/mcp, registry id biz.nibiashara/shelves) and use the job-named tool for this shelf, or buy_shelf as an escape hatch.

Calling this repeatedly? Buy a Shelf Pass once ($0.99 for 110 credits) and send X-SHELF-PASS: <token> instead of paying per call — this shelf costs 5 credits per call.

Example response (illustrative shape, not a live rate)

{
  "shelf": "cyber-insights",
  "publisher": "Ni Biashara",
  "canonical_url": "https://nibiashara.biz/shelf/cyber-insights",
  "license": "https://nibiashara.biz/terms#data-license",
  "query": {
    "insight_category": null
  },
  "count": 6,
  "results": [
    {
      "applies_to": "Homes, small shops, churches and offices with older garage/gate systems",
      "as_of": "2026-11-20",
      "category": "RF / sub-GHz access",
      "check_your_own_exposure": [
        "Find the model number on your garage or gate opener and its manual: if the remote pairs with physical DIP switches or a fixed learn procedure with no rolling-code logo (Security+, KeeLoq, or similar), it is a fixed-code system.",
        "Count your remotes. Every lost, ex-employee, or previous-tenant remote on a fixed-code system is a standing key you cannot revoke individually.",
        "Walk your perimeter: gates, dumpster enclosures and side doors on the same receiver inherit the same weakness as the main door."
      ],
      "harden": [
        "Replace fixed-code receivers/remotes with rolling-code (hopping-code) systems; the receiver upgrade is usually the cheap half of the pair.",
        "When a remote is lost, clear the receiver memory and re-pair only the remotes in hand — do not just buy a spare.",
        "Put gates and garages on the same off-boarding checklist as keys and alarm codes when staff or tenants change."
      ],
      "id": "insight-fixed-code-remotes",
      "source": "Ni Biashara defensive-awareness notes, 2026-11-20. General public security guidance; aligned with CISA consumer physical-security guidance. No offensive procedure is described or sold.",
      "title": "Legacy garage & gate remotes: fixed-code vs rolling-code",
      "what_a_consumer_tool_shows": "Inexpensive RF tools in the Flipper Zero class can demonstrate, in seconds, the difference between a legacy fixed-code remote (the same signal every press — garage and gate remotes from the DIP-switch era, still common on older 315/390/433 MHz systems) and a modern rolling-code remote (a new code every press). A signal that never changes can be captured once and replayed later; a rolling code c...",
      "what_it_means": "If your premises still run fixed-code remotes, anyone who has ever been in radio range while a button was pressed — a parking lot, a delivery, a former employee — potentially holds a copy of your key. There is no log and no way to revoke one remote: the code is the same for all of them."
    },
    {
      "applies_to": "Small offices, gyms, churches, clinics, multi-tenant buildings",
      "as_of": "2026-11-20",
      "category": "NFC / RFID access control",
      "check_your_own_exposure": [
        "Ask your landlord or access vendor one question: 'Are our credentials UID-only, or encrypted?' If they cannot answer, assume UID-only until proven otherwise.",
        "Check what a phone's free NFC reader shows for your own badge (on your own card, with permission): UID-only cards announce their identifier to any reader in range; encrypted credentials do not hand over a usable copy.",
        "Review who holds badges: unreturned badges from former staff on a UID-only system are live keys."
      ],
      "harden": [
        "Specify encrypted credentials (MIFARE DESFire EV2/EV3, HID Seos, or equivalent) at the next badge purchase — the card cost difference is small, the reader is usually already compatible.",
        "Add a PIN or phone-based second factor on the doors that matter most (office, stockroom, server/network closet) instead of re-platforming everything at once.",
        "Deactivate lost and former-staff badges the same day; keep a badge register and reconcile it quarterly."
      ],
      "id": "insight-badge-cloning-risk",
      "source": "Ni Biashara defensive-awareness notes, 2026-11-20. General public security guidance. No offensive procedure is described or sold.",
      "title": "Access badges: UID-only cards can be copied; encrypted credentials cannot",
      "what_a_consumer_tool_shows": "Consumer NFC/RFID tools can read the identifier of a proximity badge at wallet distance. For older 125 kHz prox cards and UID-only 13.56 MHz cards (including early MIFARE Classic deployments), that identifier is the whole credential — a copy of the number is a copy of the badge. Modern encrypted credentials (DESFire EV2/EV3, HID Seos) answer readers with cryptography instead of a reusable number.",
      "what_it_means": "Many small offices, gyms and older buildings still issue UID-only badges. Those badges can be duplicated without ever leaving the owner's pocket for more than a moment, and the door log will show the original holder's identity, not the copy."
    },
    {
      "applies_to": "Anyone carrying a smartphone; front-of-house staff especially",
      "as_of": "2026-11-20",
      "category": "Bluetooth / BLE",
      "check_your_own_exposure": [
        "Review your phone's Bluetooth pairing list and remove devices you do not recognize or no longer use.",
        "Check whether your phone shows a name that identifies you or your business to every nearby scanner; a neutral device name leaks less.",
        "Ask staff: has anyone here ever tapped 'Pair' or 'Allow' on a prompt they weren't expecting? That answer is your current exposure."
      ],
      "harden": [
        "Keep phone OS updates current — the spam and crash bugs in this class are patched regularly and unpatched phones stay vulnerable.",
        "Turn Bluetooth off when it is not in use, especially in crowded public places.",
        "Never accept a pairing request you did not start, and treat a sudden storm of pop-ups as a signal to walk away and toggle Bluetooth off, not to tap through it."
      ],
      "id": "insight-ble-spam-pairing",
      "source": "Ni Biashara defensive-awareness notes, 2026-11-20. General public security guidance. No offensive procedure is described or sold.",
      "title": "Bluetooth pop-up storms and unexpected pairing prompts",
      "what_a_consumer_tool_shows": "Flipper-class tools and phone apps can flood nearby devices with Bluetooth Low Energy pairing pop-ups (the 'BLE spam' demonstrations widely shown for Apple and Android devices). It is mostly a nuisance — a screen full of prompts, occasional app crashes on unpatched phones — but it trains people to tap 'Pair' or 'Connect' just to make it stop.",
      "what_it_means": "The real risk is habit, not the pop-ups themselves: a person conditioned to accept unexpected pairing prompts is one tap away from pairing with something they shouldn't — a rogue accessory, a skimming attempt, or a social-engineering setup in a crowded place."
    }
  ],
  "posture": "Defensive awareness and hardening only — what consumer RF/NFC/BLE/USB tools demonstrate, what it means for your own systems, how to check your own exposure, how to harden. No offensive content.",
  "source": "Ni Biashara cybersecurity shelf — defensive insights set",
  "as_of": "2026-11-20",
  "illustrative": true
}

Delivers

JSON { count, results[] (title, category, applies_to, what a consumer tool shows, what it means, check your own exposure, harden), posture, source, as_of }

← all shelves