LieDetector

92SECURITY | OSINT REPORT - VERIFIED & SEALED TRACK ID: IAF-VUAVS-061126 DATE: 06 NOV 2026 Source: @Irves_Watch STATUS: VERIFIED - NO MATERIAL ERRORS REMAIN ANALYST: Faisal | @92security IAF E35L - VUAVS - Air HQ Communication Squadron "Pegasus" - Palam AFS, Delhi VERIFIED FINDINGS: 1. PLATFORM: Embraer ERJ-135BJ Legacy 600 (E35L) Fleet: 4x Aircraft - K3601 Meghdoot, K3602 Vayudoot, K3603 Nabhdoot, K3604 Gagandoot - Inducted 2005 Callsign VUAVS - Documented, linked to K3601 Role: VIP / Staff Transport - NOT Combat Platform Distinct from B777-300ER / B737 BBJ for President / VP / PM 2. GEOINT: Palam AFS / VIDP - 28.57°N, 77.11°E Original tracker coord 28.4770, 78.9311 flagged as display offset. Corrected via landmark correlation: Najafgarh Jheel, Chandu, Sultanpur National Park 3. TECHINT: Speed 0 km/h = Pre-departure / Taxi Altitude 3634 m flagged as tracker convention anomaly. Field elevation ~237 m. Anomaly explained, not hidden. 4. CONTEXT: Fleet 20+ years old. Refurbishment ongoing. MoD RFI 2025-2026 for 4-6 replacement long-range business jets. Routine sustainment, NOT surge. FINAL ASSESSMENT: Single platform. No fighter, No AEW&C, No Tanker, No multi-asset coordination. Indicator Level: LOW - ROUTINE Escalation: NONE METHODOLOGY: Verify Location -> Verify Platform -> Flag Anomaly -> Assess Context -> Then Conclude. No panic. Only process. END OF REPORT Faisal | @92security Multidisciplinary OSINT -> GEOINT -> SOCMINT -> NETINT -> TECHINT -> OSINF -> IMINT -> SIGINT Products with TRACK ID | BrassTacks Archive brasstackspk.org/en 92SECURITY | TRACK ID: IAF-VUAVS-061126 06 NOV 2026 #OSINT #GEOINT #TECHINT #ADSB #IAF #Aviation #Palam #Delhi #92Security

92SECURITY | TECHINT SERIES TRACK ID: TECHINT-2026-054 | INS KOLKATA - PNS HUNAIN MARITIME FACT CHECK — 15 SEPTEMBER 2026 COLLISION CLASSIFICATION: UNCLASSIFIED // OSINT 1. CONTACT — 15 SEPT 2026 — CONFIRMED Contact/collision between naval vessels on evening of 15 September 2026, North Arabian Sea. Both governments acknowledged incident and exchanged diplomatic protests. 2. VESSEL IDENTIFICATION — QUALIFIED India's MEA (18 September, Randhir Jaiswal) explicitly named both INS Kolkata (Kolkata-class guided-missile destroyer, D63) and PNS Hunain (Batch-II Yarmook-class OPV based on Damen OPV 2600 design, F-273, commissioned 2024). Pakistan's Foreign Ministry public statements confirmed contact between an Indian vessel and a Pakistani naval ship during SEASPARK-2026, but core public FO statements do not name PNS Hunain. 3. LOCATION — REPORTED, NOT CONFIRMED COORDINATE Approximately 120 NM (220 km) east of Oman, according to Indian media reporting. No publicly available primary sensor evidence was identified in the sources reviewed that independently fixes the exact point of contact. 4. INDIAN MEA POSITION — 18 SEPT — OFFICIAL STATEMENT MEA stated INS Kolkata was on routine deployment in western/northern Arabian Sea. India described the Pakistani ship's actions as unacceptable and unprofessional and alleged a dangerous overtaking manoeuvre resulting in collision. India invoked Article 10 of the Agreement between India and Pakistan on Advance Notice of Military Exercises, Manoeuvres and Troop Movements and COLREGS. Article 10's three-nautical-mile provision is presented as India's interpretation and allegation of a breach, not as a settled legal finding. Official Indian assessment: INS Kolkata sustained no major damage and remained at sea. 5. SUBSEQUENT OPERATIONAL ACTIVITY — AZINI — 02 NOV 2026 — CORROBORATED On 2 November 2026, Indian Navy tasked INS Kolkata to intervene, with maritime reconnaissance and other support; the operation rescued all 20 crew members of hijacked Iranian FV Azini more than 3,000 km from Mumbai. Defence Minister Rajnath Singh statement + multiple outlets identify vessel. Released imagery identifies the vessel as INS Kolkata (D63). This corroborates INS Kolkata's subsequent operational deployment after September incident. This is evidence of later deployment, not proof that INS Kolkata suffered no damage in September or required no repairs. 6. PAKISTAN SEASPARK-2026 + PAK NARRATIVE — CONFIRMED DATES, ATTRIBUTED CLAIM Exercise began 1 September 2026 and concluded 14 October 2026. Opening brief reported ~3 September under CNS Admiral Naveed Ashraf. Pakistan's Foreign Ministry stated that the incident occurred while the Navy was conducting SEASPARK-2026 and alleged aggressive Indian manoeuvres in dangerously close proximity resulting in contact. 7. PNS HUNAIN DAMAGE — REPORTED, NOT INDEPENDENTLY VERIFIED Claims of large dent / possible crack on bow and return to harbour originate from Indian-source reporting. No independent verification by official Pakistani assessment, authenticated public imagery, or third-party inspection publicly established. CONCLUSION — 92SECURITY OSINT ASSESSMENT - Confirmed: Contact occurred on 15 September 2026. - Vessel ID: India's MEA explicitly identified both vessels; Pakistan's public statement did not name PNS Hunain. - Pakistan's Foreign Ministry stated that the incident occurred while the Navy was conducting SEASPARK-2026. - Subsequent activity: On 2 November 2026, INS Kolkata participated in Azini rescue, corroborating continued operational deployment. - Contested: Responsibility. - Reported, not independently verified: • Exact contact coordinates and primary sensor data remain unavailable in the reviewed public sources. • Physical damage to PNS Hunain remains unverified by independent public evidence. - Unsupported: Claims either vessel sunk/destroyed. EVIDENCE HIERARCHY - Confirmed event: naval contact. - Official claims: competing accounts of responsibility. - Corroborating evidence: INS Kolkata's subsequent deployment. - Unverified reporting: PNS Hunain's alleged bow damage. - Evidence gap: precise contact coordinates and independently verified damage assessments. EVIDENCE STANDARD Confirmed contact ≠ confirmed responsibility ≠ independently verified damage assessment. Public evidence establishes the incident — not the complete sequence of events, responsibility, or the physical condition of both vessels. Educational / OSINT Awareness Only. #INSKolkata #PNSHunain

TECHINT | FAAZ BVRAAM | JF-17 09-109 | 03 NOV 2026 TRACK ID: FAAZ-IR/261103 | CLASSIFICATION: REPORTED MISSILE RELEASE / APPARENT MOTOR IGNITION — VISUALLY SUPPORTED; WARHEAD STATUS AND TARGET ENGAGEMENT UNCONFIRMED VISUAL EVIDENCE (approx. 19.7-second video): Attributed airframe serial 09-109, reported JF-17A, with orange store marked "FAAZ BVRAAM" on underwing pylon alongside unidentified white store - attribution per video and uploader, not independently authenticated. Frame-by-frame: 17.88-18.04: Store remains beneath aircraft 18.20: Bright exhaust plume at rear of red store 18.36-18.52: Store visibly separates from its original underwing position and departs ahead of aircraft in camera view, accompanied by sustained exhaust plume 18.68-19.16: Missile departs frame, mounting position clear ASSESSMENT: Visual evidence consistent with airborne missile release, apparent propulsion-motor ignition, and separation. FINAL VERDICT: - Visually supported: FAAZ-marked store carriage, apparent separation and associated propulsion plume - Not established: Live warhead, seeker activation, guidance success or target engagement - Unverified: 120km range and operational dual RF/IIR qualification SPECS - ATTRIBUTED WITH VERIFIED SOURCES: - GIDS-reported seeker detection figures: FAAZ-RF 25 km / FAAZ-IIR 40 km — per Defense News, 3 Aug 2023 defensenews.com/industry/tec… — displayed missiles were mockups at IDEF 2023 - Advertised range/speed: FAAZ family exceeding 100 km / Mach 3.5 — GIDS-reported specifications per Defense News 2023 - FAAZ-1 / FAAZ-2 distinction: FAAZ-1 100 km, FAAZ-2 180 km advertised programme range — reported by Quwa, 22 Dec 2024; not independently demonstrated quwa.org/pakistan/munitions/… - Technical architecture: Mid-course datalink + terminal IIR combination remains unverified in available primary-source documentation Evidence preservation: Original approx. 19.7s video file, available metadata, publication timestamp and uploader attribution retained for reproducibility. Alhamdulillah — evidence-led reporting distinguishes a developmental milestone from demonstrated operational capability. #PAF #JF17 #FAAZ #OSINT

Pakistan Civilian Nuclear Emergency & Fallout Survival Handbook - Technical Review FINAL is now Publication-Ready. 142 Pages. All broken links fixed. Contacts verified. Science checked against CDC, FEMA, WHO, REMM, OSHA. Independent Reference - Not Official PNRA/NDMA Publication. Always follow NRECC 0800-777-66 NDMA 051-111-157-157. #BrasstacksArchive #PakistanCivilDefense #PreparednessIsProtection

92SECURITY | TECHINT SERIES TRACK ID: TECHINT-2026-053 | iOS ZERO-CLICK DEFENSE Zero-click threats require NO user interaction. Exploitation can occur via auto-processing of messages, calls & media without user action. POTENTIAL ATTACK SURFACES (not evidence of active exploit): iMessage, FaceTime, WebKit, Media/Image/PDF/Font parsers — commonly referenced in zero-click research as areas that process untrusted content. HARDENING — NTISB ADVISORY NO. 02/2024 + APPLE SECURITY GUIDANCE: 1. Lockdown Mode ON (Settings > Privacy & Security) - to reduce the attack surface and protect against certain sophisticated threats. No mode guarantees prevention of all infections. [NTISB No. 02/2024] 2. Install the latest iOS version available for your device. Enable Background Security Improvements → Automatically Install (Settings > Privacy & Security > Background Security Improvements). Available on supported devices running compatible software, including iOS 26.1 and later, this mechanism provides additional security protections between software updates. Availability depends on device and OS compatibility. [Apple] 3. Additional Apple precautions: Filter Unknown Senders / Silence Unknown Callers - to reduce exposure to unsolicited messages and calls. [Apple, not explicitly in NTISB No. 02/2024] 4. For high-risk: Consider disabling iMessage & FaceTime per NTISB guidance [NTISB No. 02/2024] 5. Regular reboot - may disrupt some non-persistent, memory-resident compromises, may require an attacker relying on non-persistent access to regain access or reinfect the device. Persistent malware may survive reboot. Does NOT determine compromise status. Precautionary hardening, NOT removal. Rebooting is not evidence that a device is clean. [NTISB No. 02/2024] ON FORENSICS: - Apple recommends seeking expert assistance if mercenary spyware targeting is suspected. - Qualified investigators may use forensic tools such as Amnesty International's Mobile Verification Toolkit (MVT). MVT is developed by Amnesty International Security Lab, not Apple. - MVT is a forensic tool and not intended for end-user self-assessment. - A clean MVT scan does not establish that a device is free from spyware. Public indicators alone are insufficient to establish that a device is clean. Negative forensic findings must be interpreted within the limitations of available indicators and collected evidence. - Forensic examination is distinct from regular rebooting. Sources Verified: - NTISB Advisory No. 02/2024 — Cabinet Division: cabinet.gov.pk/SiteImage/Mis… - Apple Support — Background Security Improvements: support.apple.com/en-la/1026… [Path verified: Settings > Privacy & Security > Background Security Improvements] - Apple Support — Mercenary spyware / threat notifications: support.apple.com/102174 - MVT Documentation — Amnesty International Security Lab: docs.mvt.re/ [Forensic limitations verified] Educational / OSINT Awareness Only. #TECHINT #OSINT #iOSSecurity

Our Beloved Syed Zaid Hamid Sahab says... JAAC IS THAT ENEMY. THEY DON'T WANT SOLUTIONS. THEY WANT PAKISTAN TO COLLAPSE FROM INSIDE, JUST LIKE 1971. WAKE UP BEFORE IT'S TOO LATE. EVERY NATION HAS ENEMIES AT THE BORDER. BUT THE MOST DANGEROUS ENEMY IS THE ONE WHO SPEAKS YOUR LANGUAGE AND LIVES IN YOUR STREET.

TRACK ID: 2026-11-01-PK-LHR-CTD | LANE: #92_TECH INT: OSINF + GEOINT + TECHINT + IMINT — LAHORE: CTD HQ Incident | OSINT Analysis ⚡🇵🇰 | Parameter | Data | | GEOINT | CTD HQ, Jallo Park, Lahore — 31.6000°N, 74.4700°E | | TIME | ~0030 hrs, 01 Nov 2026 | | VECTOR | Inbound from Jallo Morh direction → struck outer wall → fell inside compound | | PLATFORM | High-tech surveillance craft, camera payload, lights active on recovery | | STATUS | BDS cleared as unarmed / no explosives — Forensic + Tech analysis underway | OSINF FUSION: Bol News / Dunya News / GTV report: Police assessment = suspected terrorism / sabotage / recce of sensitive facility. CTD security team submitted application at Harbanspura PS for legal action. ANALYSIS: - Profile matches low-slow-small UAS used for ISR, not kinetic - Direction of approach ( map) aligns with Jallo Morh corridor, close to Wagah border axis — needs further TECHINT on range/endurance - Cameras active post-crash indicates live-feed ISR intent, not crash due to failure No speculation on origin — Forensics pending. #OSINT #GEOINT #TECHINT #Lahore #CTD