TIGR Threat Watch

Threat Watch Feed

🚩 – IOCs Added

The red flag indicates that Indicators of Compromise (IOCs) have been added to SRA’s Threat Feed used by CyberSOC clients. Articles may not be flagged if IOCs are not available at the time or are not applicable to the article.

Check Point Research uncovers Yoba, a Malware Campaign using Fake ChatGPT and Claude Installers and DLL Sideloading to Establish Persistence and Deploy Cryptocurrency Miners on Windows Systems

Check Point Research identified Yoba, a malware campaign distributing malicious installers through fake GitHub repositories and GitHub Pages impersonating AI desktop applications, including GPT-5.6 Sol, GPT-6 Astra, and Claude Opus. The repositories appeared prominently in Google search results, suggesting SEO poisoning was used to attract potential victims. The malicious ZIP archives contain legitimate, digitally signed OpenAI or Anthropic executables alongside a malicious winmm.dll that executes through DLL sideloading. Researchers also identified an earlier Yoba variant associated with a Cursor AI-themed executable. The campaign targets users seeking AI software downloads, although the research does not identify specific victim organizations or confirm the number of compromised systems.

Once executed with administrative privileges, YobaDropper deploys YobaLoader as wmpdui.dll alongside a legitimate WMPDMC.exe executable in C:\ProgramData\WMProcess\, establishing persistence through a scheduled task running as SYSTEM. YobaLoader retrieves a Telegram channel profile image to generate a domain using a domain generation algorithm (DGA), then queries Google’s DNS-over-HTTPS service for encrypted instructions directing it to additional payloads hosted on Catbox. The loader supports process injection, executable deployment, and PowerShell execution. Check Point observed the delivery of an XMRig cryptocurrency miner injected into svchost.exe, with mining communications routed through Tor. The malware also employs process-name validation, language-based exclusions, and execution delays to evade analysis. Although the loader can deliver other payloads, additional malware families were not confirmed.

Impact: Yoba poses a threat to organizations whose users install AI-related applications from unverified repositories. Successful infection can establish persistent, SYSTEM-level malware execution, enable retrieval and execution of additional attacker-controlled payloads, and consume computing resources through unauthorized cryptocurrency mining. Its use of legitimate signed executables for DLL sideloading may complicate detection, while Telegram, DNS-over-HTTPS, and public file-hosting services help conceal payload retrieval. The loader’s flexible execution capabilities create opportunities for additional compromise, although the observed final payload was an XMRig miner. Researchers identified indicators suggesting Russian origins, but definitive attribution remains unconfirmed.

Recommendation:

  • Restrict unapproved AI software installations and require users to download applications from verified vendor distribution channels rather than unfamiliar GitHub repositories.

  • Monitor DLL sideloading activity involving signed Setup.exe processes loading unexpected winmm.dll files from local installation directories.

  • Hunt for persistence artifacts involving scheduled tasks configured to execute WMPDMC.exe from C:\ProgramData\WMProcess\ under the SYSTEM account.

  • Review GitHub access and download telemetry for identified malicious repositories, including github[.]com/gpt-5-6/sol-free-desktop, gpt-6-astra[.]github[.]io, and opus-5-0[.]github[.]io.

  • Monitor suspicious network communications involving t[.]me/yoba_fanclub, files.catbox[.]moe/z5zpy9.dat, and dynamically generated domains following the pattern adjective-noun-verb-number.dedyn[.]io.

  • Hunt for unusual DNS-over-HTTPS requests and process injection, particularly Google DNS TXT lookups for unfamiliar generated domains, suspicious injection into svchost.exe, and hidden PowerShell execution.

  • Deploy Check Point’s published YARA rules for YobaDropper and YobaLoader, and investigate unauthorized XMRig mining, Tor activity, and suspicious CPU utilization.

ANY.RUN identifies SkyW4lker, an Active Phishing Kit Targeting Microsoft 365 users through Device-code Authentication Abuse that can Enable Unauthorized Account Access despite MFA Protections

ANY.RUN researchers identified SkyW4lker (SkyW4lker x365 Sentinel), an active phishing kit targeting Microsoft 365 users across the United States, Europe, and other regions. The campaign uses phishing emails containing password-protected PDF, DOCX, or Excel attachments, often disguised as contracts, invoices, commercial offers, or confidential documents. Victims are directed through CAPTCHA challenges and intermediary pages, sometimes hosted on legitimate services such as Google Sites, Miro, or Zoom, before reaching a page instructing them to enter a device code through Microsoft’s legitimate authentication service. ANY.RUN identified 618 related sandbox analyses, with approximately 46% originating from the United States and additional activity associated with India, Canada, and the United Kingdom. Submissions were primarily associated with technology, manufacturing, and government organizations.

SkyW4lker abuses the Microsoft OAuth 2.0 device-code authentication flow, allowing attackers to obtain access tokens when victims authorize an attacker-initiated authentication request. The kit uses obfuscated JavaScript and a PHP backend to collect visitor information, track authentication progress, and poll /session_public.php?action=poll until the victim completes the authentication process. Its supporting modules include client_geo.js, url_helper.js, and endpoint.js, which handle geolocation, URL processing, and authentication-related data collection. Researchers also identified an administration panel supporting victim monitoring and phishing link management. ANY.RUN assesses with high confidence that SkyW4lker and the Gabagool credential phishing kit share the same developer based on overlapping JavaScript modules, URL patterns, and hosting infrastructure. However, the research does not establish whether both kits are operated by the same threat actor or multiple customers. Active phishing activity is confirmed through sandbox analyses, although the provided research does not establish a verified number of successfully compromised Microsoft 365 accounts.

Impact: SkyW4lker poses a significant identity security risk by exploiting legitimate Microsoft authentication functionality rather than relying solely on traditional password theft. Successful device-code phishing could provide attackers with unauthorized access to Microsoft 365 accounts, potentially exposing corporate email, sensitive documents, and other resources available to the compromised identity. Because victims authenticate through legitimate Microsoft services, MFA alone may not prevent account compromise when users approve an attacker-initiated device-code request. The campaign’s use of familiar business documents, trusted hosting platforms, and CAPTCHA challenges can also complicate email security filtering and automated phishing detection. Compromised accounts could enable additional unauthorized access, information theft, and follow-on phishing against employees or business partners. However, the extent of successful account compromise and subsequent malicious activity remains unconfirmed in the provided research.

Recommendation:

  • Restrict unnecessary device-code authentication through Microsoft Entra Conditional Access policies. Block the device-code flow where it is not required for legitimate business operations.

  • Monitor Microsoft Entra ID sign-in logs for unusual device-code authentication activity, particularly authentication attempts associated with suspicious emails, unexpected geographic locations, or unfamiliar devices.

  • Hunt for SkyW4lker phishing infrastructure and URL patterns, including /session_public.php?action=start, /session_public.php?action=poll, and repeated requests containing session identifiers.

  • Investigate suspicious JavaScript and PHP components associated with the phishing kit, including /assets/js/client_geo.js, /assets/js/endpoint.js, /assets/js/url_helper.js, and /assets/php/endpoints/confirm_visit.php.

  • Review email security telemetry for password-protected attachments containing links to external document portals, particularly messages impersonating contracts, invoices, financial statements, or confidential business correspondence.

  • Inspect suspicious redirection chains involving Google Sites, Miro, Zoom, Google Maps, and other legitimate services when they lead to unfamiliar Microsoft-themed authentication or document-sharing pages.

  • Monitor access to identified phishing infrastructure, including 5200m[.]com, torvion[.]life, ghethim[.]com, flow505[.]mooo[.]com, and off365acess[.]jumpingcrab[.]com, while accounting for possible infrastructure changes.

  • Correlate phishing indicators with Microsoft 365 activity, including unexpected mailbox access, document retrieval, unusual account activity, and subsequent authentication events following suspected device-code phishing.

  • Educate employees about device-code phishing, emphasizing that legitimate Microsoft authentication pages can still be abused when users enter codes supplied by unsolicited emails, documents, or unfamiliar websites.

  • If account compromise is suspected, revoke active sessions and refresh tokens, investigate associated Microsoft 365 access, review potentially exposed resources, and determine whether additional accounts or business applications were affected.

Zscaler Uncovers an SEO Poisoning Campaign Impersonating Chocolatey and Microsoft Activation Scripts to Distribute Armorsteal

On October 22, 2026, Zscaler Threat Hunting disclosed an SEO poisoning campaign distributing Armorsteal, a newly identified Python-based malware family targeting Windows users searching for Chocolatey package manager installation instructions and Microsoft Activation Scripts (MAS). First identified in September 2026, the campaign used fraudulent websites impersonating legitimate software projects, including choclatey[.]org and massgravel[.]net, to trick users into executing malicious PowerShell installation commands. The fake Chocolatey installer also executed the legitimate installation process, allowing the software to appear functional while silently deploying malware. Both installer variants requested elevated privileges, concealed the PowerShell console, and downloaded an archive containing a Python 3.11 runtime and Pyarmor-protected malware components into C:\Windows\SystemHealth\Update\. Persistence was established through scheduled tasks named SysCheck2 and SysCheckX, configured to execute the remote access module at user logon and system startup, respectively. Researchers linked both distribution websites to the same operation through shared malware components, command-and-control (C2) infrastructure, and an RSA-2048 task-signing key. The fake websites were taken offline by early October, although the operators subsequently modified their infrastructure.

Armorsteal consists of three primary components providing remote access, surveillance, and information theft. The remote access module, SysMon.py, collects system information, communicates with attacker-controlled infrastructure over HTTPS, and polls for new tasks every 60 seconds. Received Python tasks are verified using embedded RSA-2048 signatures before being executed in memory, while version tracking prevents previously executed tasks from running again. The surveillance module, basrq.py, records keystrokes and active window titles, monitors clipboard activity, captures screenshots based on configured keywords, and replaces cryptocurrency wallet addresses with attacker-controlled addresses. The information-stealing module, got.py, extracts browser cookies, saved passwords, Discord tokens, cryptocurrency wallet data, BIP39 seed phrases, SSH keys, and password manager information. It also uses the Chrome DevTools Protocol on port 9222 and downloads a publicly available Chrome decryption tool to access protected browser credentials. Armorsteal employs Pyarmor obfuscation and cloud-environment detection to complicate analysis. Zscaler identified infrastructure changes involving workerstats[.]net, pymons[.]is, and datamons[.]org, demonstrating continued operational adjustments during the investigation.

Impact: Armorsteal presents a significant threat to organizations through unauthorized remote access, credential theft, persistent surveillance, and financial fraud. Successful infection could allow attackers to execute additional Python payloads, capture employee keystrokes and screenshots, steal browser authentication cookies, and compromise accounts associated with password managers, Discord, and other applications. Its cryptocurrency clipboard hijacking and seed phrase collection capabilities could enable theft of digital assets, while stolen SSH keys and authentication data may provide opportunities for additional unauthorized access. The use of scheduled tasks with elevated privileges supports persistence across system restarts, and its remote task execution functionality allows operators to modify malware behavior after initial compromise. The campaign’s use of legitimate software installation instructions increases the likelihood of users executing malicious commands, particularly administrators and developers who regularly install software through PowerShell. Although Zscaler confirmed the malware’s capabilities and distribution infrastructure, the research does not establish a specific victim count or confirm broader enterprise compromise.

Recommendation:

  • Block and monitor identified malicious infrastructure, including choclatey[.]org, massgravel[.]net, workerstats[.]net, pymons[.]is, datamons[.]org, niceer[.]net, and supertrap[.]net.

  • Hunt for suspicious scheduled tasks named SysCheck2 and SysCheckX, particularly tasks configured to launch Python executables at user logon or system startup with elevated or SYSTEM privileges.

  • Inspect endpoints for unauthorized files and directories beneath C:\Windows\SystemHealth\Update\, including SysMon.py, basrq.py, got.py, bundled Python runtimes, and associated ZIP archives.

  • Review PowerShell execution logs for suspicious installation commands, hidden console execution, privilege elevation, and downloads originating from choclatey[.]org, community[.]choclatey[.]org, or massgravel[.]net.

  • Monitor outbound HTTPS traffic for Armorsteal C2 activity, including requests to /receive_infof, /get-global, /get-onetime-code/, /black-watch/, and /infame/receive/, where URL paths are visible in network telemetry.

  • Investigate browser processes launched with –remote-debugging-port=9222, particularly when associated with unexpected Python processes or unauthorized access to browser authentication data.

  • Monitor endpoint behavior associated with credential theft, including suspicious access to password manager databases, browser cookie stores, SSH private keys, Discord tokens, and cryptocurrency wallet files.

  • Review Microsoft Defender exclusions and endpoint security configurations for unauthorized changes, particularly exclusions affecting C:\Windows, which may allow malicious components to evade security scanning.

  • Restrict untrusted PowerShell installation commands through application control policies, least-privilege access, and approved software installation procedures. Educate users to verify official software domains before executing commands copied from search results.

  • If Armorsteal is detected, isolate affected endpoints and investigate persistence, remove malicious scheduled tasks and payloads, revoke potentially compromised authentication sessions, rotate exposed credentials, and assess cryptocurrency wallet exposure.

Critical Broccoli2Shell Vulnerability In The Brotli Decoder Exposes Node.js, Bun, Envoy, Istio, and Other Applications to Potential Unauthenticated Remote Code Execution.

On October 25, 2026, Wiz published an advisory detailing CVE-2026-111497, also known as Broccoli2Shell, Node2Shell, or HTTP2Shell, a critical out-of-bounds write vulnerability affecting the Brotli decompression library. The vulnerability was discovered by Khai Tran and Sylvie Mayer of OpenAI Codex Security and originates in the upstream Brotli C decoder, affecting downstream technologies including Node.js, Bun, Envoy Proxy, Istio, and Python Brotli packages. The flaw occurs when the decoder improperly processes specially crafted compressed data, allowing an unauthenticated attacker to trigger memory corruption. Successful exploitation could result in sensitive memory disclosure, application crashes, or arbitrary code execution with the privileges of the affected process. Researchers have demonstrated exploitation against unpatched Node.js environments. According to Wiz, 91% of cloud environments contain resources vulnerable to CVE-2026-111497, while 82% have publicly exposed Node.js instances. These figures describe separate exposure measurements and do not establish that all publicly exposed Node.js instances are exploitable.

Exploitation requires a vulnerable application or dependency to decompress attacker-controlled Brotli data, potentially delivered through HTTP requests, externally retrieved responses, uploaded files, or other untrusted compressed content. Some HTTP clients and application frameworks automatically decompress Brotli-encoded responses, creating potential exposure even when applications do not explicitly reference Brotli. The vulnerability is particularly relevant to containerized applications, Kubernetes clusters, API gateways, reverse proxies, serverless functions, and cloud-hosted services. Affected versions include Brotli 1.0.3–1.2.0 excluding patched backports, unpatched Node.js 22.x/24.x/26.x releases, Bun 1.0.21–1.4.3, and specified Envoy and Istio releases. Security updates are available, including Node.js 22.23.4, 24.22.1, and 26.12.1, Bun 1.4.4, Brotli 1.2.1, and vendor-specific fixes for Envoy and Istio. Although successful exploitation has been demonstrated in a research environment, the provided advisory does not establish active exploitation in the wild.

Impact: CVE-2026-111497 presents a risk to organizations operating applications and infrastructure that decompress untrusted Brotli-compressed data. Successful exploitation could allow unauthenticated attackers to corrupt application memory, disclose sensitive information, terminate processes, or potentially execute arbitrary code within the affected runtime or container. Compromised workloads could expose application credentials, sensitive business data, and other resources accessible to the vulnerable process. Application crashes may also disrupt service availability, particularly in environments relying on affected reverse proxies, API gateways, or shared infrastructure components. The vulnerability’s presence in widely adopted upstream and downstream dependencies increases the potential exposure across cloud environments, including applications that perform decompression indirectly.

Recommendation:

  • Remediate of CVE-2026-111497 by updating affected Brotli libraries and downstream components to vendor-supported patched versions, including Brotli 1.2.1, Node.js 22.23.4/24.22.1/26.12.1, and Bun 1.4.4, or applicable patched backports.

  • Update vulnerable Envoy Proxy deployments to patched releases 1.36.12, 1.37.8, 1.38.6, 1.39.3, or 1.40.0, depending on the deployed release branch.

  • Remediate affected Istio installations by upgrading to 1.29.9, 1.30.6, or 1.31.2, or later supported releases containing the fix.

  • Review Python and Go dependencies for vulnerable Brotli implementations, including Python brotli, brotlicffi, and andybalholm/brotli, updating to their respective patched versions.

  • Inventory cloud workloads and application dependencies across virtual machines, Kubernetes clusters, containers, serverless functions, API gateways, and reverse proxies to identify vulnerable Brotli components, including statically linked and transitive dependencies.

  • Prioritize internet-facing applications and services processing untrusted compressed data, including HTTP request bodies, externally retrieved responses, file uploads, and applications performing automatic Brotli decompression.

  • Rebuild and redeploy affected application workloads after updating dependencies, container base images, and lockfiles. Restart affected processes and verify that patched library versions are loaded at runtime.

  • Implement temporary mitigations where patching is delayed, including disabling Brotli decompression, rejecting Brotli-encoded requests before they reach vulnerable components, or restricting the processing of untrusted compressed responses where operationally feasible.

  • Monitor WAF, application, and network telemetry for suspicious Brotli-compressed requests, unusual compressed payloads, repeated application errors, and abnormal behavior involving Brotli-enabled services.

  • Hunt for potential exploitation indicators, including unexpected process crashes, memory corruption errors, abnormal application restarts, suspicious child processes, and unauthorized code execution originating from vulnerable application runtimes.

Check Point Research uncovers Aokigahara, an Infostealer Targeting AI Application Sessions, Developer Credentials, Cloud Authentication Data, and Traditional Browser Secrets.

On October 23, 2026, Check Point Research disclosed Aokigahara, a newly observed infostealer identified in the wild that expands traditional credential theft to include AI applications and developer environments. Earlier versions of the malware may have been known as Kamidere or Stygian. Aokigahara targets authentication files, session data, and configuration files associated with ChatGPT Desktop, Claude, Codex, Cursor, Windsurf, GitHub Copilot, Gemini CLI, and other AI-assisted development tools. Its collection capabilities also extend to AWS, Azure, and Google Cloud credentials, Git authentication files, SSH private keys, browser passwords and cookies, cryptocurrency wallets, VPN configurations, password managers, and messaging applications. The malware can capture screenshots and clipboard contents, collect files from user directories, and deploy a separate cryptocurrency clipboard-manipulation component. Although the malware has been observed in the wild, the research does not establish a specific distribution method, threat actor attribution, or confirmed victim count.

Aokigahara uses a modular architecture controlled by an encrypted configuration stored in the .stgcfg section, which contains its command-and-control (C2) configuration, enabled collection modules, and anti-analysis settings. The malware employs AES-256-CBC to decrypt its configuration and uses an X25519 key exchange to establish encrypted communications with its C2 infrastructure. Collected data is packaged into ZIP archives, encrypted using AES-256-GCM, and transmitted through HTTP POST requests to /gate/handshake, /gate/chunk, and /gate/complete. The malware also implements optional anti-debugging, virtual machine detection, sandbox checks, and language-based execution restrictions that include Russian, Ukrainian, Belarusian, and several other regional language settings. Its use of dynamic Windows API resolution and control-flow obfuscation further complicates analysis. While the malware’s collection capabilities are confirmed through code analysis, researchers did not establish how operators monetize the stolen information.

Impact: Aokigahara presents a significant credential theft and data exposure risk to organizations using AI-assisted development tools, cloud platforms, and traditional enterprise applications. Compromised AI authentication tokens or session data could potentially allow attackers to access paid AI services, private conversations, uploaded documents, and sensitive development information, depending on the permissions and validity of the stolen credentials. Exposure of Git credentials, SSH private keys, and cloud authentication files could facilitate unauthorized repository access, cloud resource compromise, and additional intrusion activity. Browser session theft and password manager targeting may also enable account takeover, while the malware’s clipboard-manipulation component introduces potential cryptocurrency theft risks. Although these capabilities create opportunities for financial fraud, unauthorized AI service consumption, and data extortion, the research does not confirm that these downstream activities have occurred.

Recommendation:

  • Deploy and maintain endpoint detection and response (EDR) protections capable of detecting infostealer behavior, including suspicious credential-store access, browser cookie extraction, screenshot capture, and unauthorized collection of application configuration files.

  • Monitor access to AI application authentication files, including .claude\credentials.json, .codex\auth.json, ChatGPT Desktop application storage, and authentication-related files associated with Cursor, Windsurf, GitHub Copilot, and Gemini CLI.

  • Audit developer workstations for suspicious access to sensitive files, particularly .aws\credentials, .aws\sso\cache, .ssh private keys, Git credential files, and cloud configuration directories.

  • Hunt for suspicious HTTP POST requests involving /gate/handshake, /gate/chunk, and /gate/complete, particularly when accompanied by headers such as X-Build-ID, X-Gate-Token, X-Session, X-HWID, and X-Chunk-Index.

  • Implement the YARA detection rule published by Check Point Research to identify Aokigahara samples using embedded strings, configuration markers, and other malware-specific artifacts.

  • Investigate suspicious executable behavior associated with anti-analysis techniques, including debugger detection, virtual machine checks, dynamic API resolution, and unexpected process termination based on system language settings.

  • Restrict storage of long-lived credentials on developer endpoints by using approved secrets-management solutions, short-lived authentication tokens, and least-privilege access for AI services, cloud environments, and source code repositories.

  • Review endpoint activity for unauthorized clipboard manipulation, including suspicious executables or components created beneath C:\Microsoft\Vault, which Check Point identified as a location used by the malware’s clipper deployment mechanism.

  • If Aokigahara infection is confirmed, isolate affected systems and revoke potentially exposed credentials, including AI service sessions, API keys, cloud access tokens, Git credentials, SSH keys, browser sessions, and VPN authentication material. Review associated services for unauthorized access before restoring endpoint access.

🚩 BlackX Bootkit Exploits Baton Drop Flaw to Bypass Secure Boot on Patched Systems

Kaspersky researchers identified BlackX, a Unified Extensible Firmware Interface (UEFI) bootkit deployed in an espionage campaign in early 2026. Kaspersky attributes the campaign to APT41, with the following potential alias’s observed, Brass Typhoon, Wicked Panda, and Barium. The campaign targeted diplomatic agencies in Central Asia.

BlackX exploits the Baton Drop vulnerability (CVE-2022-21894) to bypass Secure Boot. The bootkit enrolls custom Machine Owner Keys (MOKs) and loads arbitrary EFI files. Its exploit closely matches the implementation used by BlackLotus, a bootkit circulating on hacker forums since late 2022. Kaspersky found BlackX code that is absent from the incomplete BlackLotus source code leaked in mid-2023, which indicates the operator either reverse engineered BlackLotus or obtained its source code.

BlackX injects a kernel driver signed with a revoked certificate issued to Wenjiang District Mingyu Network Technology Service Studio. The driver disables security processes and registry callbacks and tampers with Event Tracing for Windows (ETW) providers. Some tampering runs only when Kaspersky or Avast products are present on the host. The driver launches Windows Calculator when a user attempts to open the bootkit’s files. The campaign deploys a remote access trojan (RAT) that uses Google Drive, OneDrive, or Yandex.Disk for command-and-control (C2), along with OxiDLLRunner, an obfuscated DLL sideloaded by googleupdate.exe.

Impact: BlackX loads a malicious driver that disables security processes, registry callbacks, and ETW providers on infected hosts. Kaspersky states that every BlackX victim ran a fully patched Windows release. The bootkit succeeded because administrators did not manually activate the additional Secure Boot revocations that the Baton Drop patch requires. The payloads provide remote access and retrieve DLL plugins from archivetj[.]com.

Recommendation:

  • Apply the Baton Drop patch for CVE-2022-21894 on all Windows systems, following Microsoft’s published instructions.

  • Manually activate the Secure Boot revocation for the Windows Production PCA 2011 certificate, as the patch does not trigger it automatically.

  • Add the Windows Production PCA 2011 certificate to a blocklist, since its October 19, 2026 expiration does not prevent vulnerable binaries from loading.

  • Confirm that endpoints reject drivers signed by the revoked certificate issued to Wenjiang District Mingyu Network Technology Service Studio.

  • Block outbound access to archivetj[.]com.

Sign up here!

To receive the TIGR Threat Watch email bulletin and critical vulnerability notifications, simply complete the form below.

 

Follow on Twitter

@SRA_ThreatWatch will keep you up to date with the most recent posts on your social media feed.

Subscribe to the RSS

Just copy and add this link to your RSS app and be notified immediately when new intel is posted.

How to use RSS

Following the RSS feed is easy. RSS can be added in your Outlook desktop app, and there are many free RSS readers available for your mobile device.

To follow using Outlook:

  • In Outlook, right-click the RSS Feeds folder and choose Add a New RSS Feed.
  • In the New RSS Feed dialog box, enter the URL of the RSS Feed: https://sra.io/category/tigr/feed

(click here for detailed instructions and additional options for Outlook)

Popular mobile RSS reader apps include:

  • Feedly
  • NewsBlur
  • RSS Reader
  • Inoreader

After installing your preferred RSS reader, you will be able to add this feed by entering the URL: https://sra.io/category/tigr/feed

Threat Bulletin Archive

About TIGR Threat Watch

Our Threat Intelligence Gathering & Research (TIGR) team is focused on threat intelligence and curates a daily intelligence report, TIGR Threat Watch, with information collected from several industry intel sources. We also create and publish ad-hoc critical vulnerability notifications in case of critical and time-sensitive vulnerabilities or threats. These notifications include details and recommendations for mitigation/remediation.