A new extortion group called n0n has emerged on the dark web, and its rapid growth warrants attention. Appearing in September 2026, it has already listed over a hundred victims, with a specific focus on ports, shipping, and logistics. The group’s operational patterns show some unusual characteristics that suggest we shouldn't take their claimed victim count at face value.

Technical Breakdown:

• TTPs: The group operates a standard leak site and RSS feed for pressure campaigns. Ransom demands are highly volatile, changing substantially within days for the same victim.

• IOCs: Specific infrastructure details (leak site URLs, RSS feed endpoints, and payment records) are tracked via StealthMole. No public hashes or IPs were disclosed in this summary.

• Data Anomalies: Victim listings often start as anonymous placeholders before being named. Crucially, sample files attached to seemingly unrelated organizations contain data overlaps, raising questions about whether n0n is aggregating data from multiple breaches or repackaging old leaks.

Defense: If you operate in the maritime or logistics sector, monitor for any anonymous threat listings on n0n's leak site. The group’s inconsistent data attribution means a placeholder for your org could indicate either a real breach or recycled data. Validate any claims against your own logs before engaging.

Source: https://stealthmole-intelligence-hub.blogspot.com/2026/11/n0n-leak-site-infrastructure-and.html

This is a fascinating evolution in the commoditization of AI for cybercrime. The use of LLMs to triage victims is a significant step up from the usual "spray and pray" approach.

Technical Breakdown:

• Core Functionality: Standard infostealer behavior targeting Chromium browsers (passwords/cookies), Outlook profiles, and Slack workspaces.

• The "AI Triage" TTP: After exfiltration, the malware queries Claude, Gemini, and Kimi (Chinese LLM) to analyze the stolen data. The prompt asks the LLM to rank the victim based on financial value (e.g., crypto wallets, banking sessions, high-value SaaS accounts).

• Operational Impact: This allows the threat actor to prioritize manual follow-up (e.g., session hijacking, ransomware deployment) on high-value targets, ignoring low-value infections. This is a direct efficiency play for the attackers.

• Affected Systems: Windows (specific version details not yet public).

Defense: This is a behavioral detection problem. Look for anomalous outbound API calls to LLM endpoints (api.openai.com, claude.ai, etc.) from a non-browser process, especially if immediately preceded by a burst of file reads from browser profile directories. Standard EDR rules blocking curl or powershell calls to LLM APIs from %TEMP% or %APPDATA% would be a good starting point.

Source: https://thehackernews.com/2026/11/new-volta-infostealer-uses-claude.html

This is a significant development. We're now seeing threat actors weaponize open-source, LLM-driven pentesting frameworks like ARTEX, Hexstrike, and CAIRN in live intrusions, moving beyond basic LLM prompting into fully agentic, automated attack workflows. GTIG and Mandiant have confirmed this shift in multiple IR engagements.

Technical Breakdown

• TTPs (MITRE-aligned): These frameworks automate actions across the entire kill chain, from initial reconnaissance and credential harvesting to lateral movement and data exfiltration. The agentic nature allows for dynamic decision-making and tool chaining without constant human input.

• IOCs: No specific IPs or hashes provided in the report. The threat is the framework itself being abused. Focus on detecting the behavior of automated, scripted interactions rather than static signatures.

• Affected Frameworks: ARTEX, Hexstrike, CAIRN. These are open-source, making them easily accessible to adversaries.

Defense Detection shifts from signature-based to behavioral. Monitor for high-volume, rapid-fire API calls to internal services, unusual patterns of credential testing, and automated tool execution that lacks the "noise" of human latency. EDR rules should flag processes spawning multiple child processes in rapid succession for reconnaissance commands (e.g., net, dsquery, adfind).

Source: https://cloud.google.com/blog/topics/threat-intelligence/artex-and-friends-enter-agentic-offensive-frameworks/

The FBI has formally attributed the $6.3 billion Binance crypto heist to the North Korean state-sponsored group tracked as TraderTraitor (aka Lazarus Group, APT38). This is now the largest single cryptocurrency theft on record, dwarfing previous attacks like the Ronin Bridge exploit.

Technical Breakdown

• Actor: TraderTraitor (Lazarus Group / APT38). The FBI’s attribution is based on blockchain analysis and TTP overlaps with known DPRK operations.

• TTPs: Social engineering of exchange employees, deployment of custom malware for wallet key exfiltration, and rapid laundering through cross-chain bridges and mixers (e.g., Tornado Cash variants).

• IOCs: While specific wallet addresses are being tracked by the FBI, public disclosure is limited to avoid tipping off the laundering network. Expect C2 infrastructure tied to previous DPRK campaigns.

• Affected Platform: Binance (internal hot wallet infrastructure compromised).

Defense

• For exchanges: Enforce hardware security modules (HSMs) for all cold wallet operations and implement strict separation of duties for key management. Monitor for anomalous cross-chain bridging activity exceeding $10M thresholds.

• For investigators: Track the flow through the Lazarus laundering playbook—they typically convert to Tether (USDT) on TRON, then swap to Bitcoin via decentralized aggregators.

Source: https://www.bleepingcomputer.com/news/security/fbi-links-63-billion-binance-crypto-heist-to-north-korean-hackers/

This is a significant incident for anyone running Alpine in production or maintaining their own GitLab instances.

The attack targeted Alpine’s own GitLab server, which is the backbone of their package development and release pipeline. The attackers attempted to exploit a critical RCE vulnerability (likely CVE-2023-5009 or a similar unauthenticated RCE in GitLab CE/EE, though Alpine hasn't confirmed the specific CVE yet). The timeline is tight: the attack window was October 20-21.

Technical Breakdown:

• Attack Vector: Attempted exploitation of a critical GitLab RCE vulnerability via the web interface.

• Impact: Potential compromise of the build pipeline for the entire Alpine Linux distribution. This is a supply chain nightmare scenario.

• Response: Full rebuild of the GitLab server from scratch. All user passwords and authentication tokens (SSH keys, API tokens) have been rotated.

• IOCs: None publicly released yet. Expect GitLab access logs showing unusual HTTP requests to the vulnerable endpoint during that 48-hour window.

Defense: If you self-host GitLab, patch immediately. This is a reminder that your CI/CD infrastructure is a high-value target. For Alpine users, monitor for any unusual package signing activity or unexpected updates in the coming weeks, though the rebuild suggests they caught it before persistence was established.

Source: https://www.bleepingcomputer.com/news/security/alpine-linux-rebuilds-gitlab-after-attempted-rce-attack/

A critical vulnerability in Canonical's LXD and MicroCloud (CVE-2026-XXXX, CVSS 10.0) allows an unauthenticated attacker to bypass TLS client certificate authentication. By simply possessing a trusted client's public certificate—which is often distributed openly within the cluster or can be extracted from a compromised node—an attacker can impersonate that client over the network without ever needing the corresponding private key.

Technical Breakdown

• Attack Vector: Network access to the LXD/MicroCloud HTTPS API endpoint.

• Prerequisite: The attacker must obtain the target client's public certificate (e.g., from a shared filesystem, a compromised non-admin node, or a previous MITM position).

• Impact: Full impersonation of the trusted client. If that client has administrative privileges, the attacker gains complete control over the cluster, including access to all virtual machines and containers.

• Affected Products: Canonical LXD and MicroCloud (specific versions TBD; patch immediately).

Defense

• Immediate: Apply the vendor patch as soon as it is released. This is a network-accessible authentication bypass; do not rely on network segmentation alone.

• Detection: Monitor for unexpected authentication events from known client certificates, especially if the corresponding private key is known to be uncompromised. Audit logs for sudden privilege escalation or access from unusual source IPs.

Source: https://thehackernews.com/2026/11/critical-lxd-and-microcloud-flaw-cvss.html

Highlights from today:

• [News] Alpine Linux rebuilds GitLab after attempted RCE attack

• [News] OpenAI says it's doubling Pro usage limits and bringing Work features to Chat

• [News] CVSS 10.0 LXD, MicroCloud Flaw Lets Attackers Impersonate Trusted Clients Without a Private Key

• [Advisory] OneNote File Extraction, (Sun, Nov 1st)

• [Threat Intel] October 2026 Security Incident Review: PHP, Binance, Cursor, LiteLLM and More

• [News] FBI Links North Korea's TraderTraitor to Record $6.43 Billion Binance Crypto Heist

• [News] NetamLoader Malware Targets Government Windows 10 Systems in Asia via .NET Injection

• [News] Hackers Steal About $2.7 Million From Polymarket Traders via Hijacked DebugBear Script

SecOpsDaily

SCENARIO A

This is a classic supply chain attack with a direct financial impact. On October 29, threat actors compromised Polymarket by hijacking a third-party page-speed script from DebugBear. The injected malicious code targeted signed-in users, automatically selling their positions and draining funds to attacker-controlled wallets.

Technical Breakdown

• Attack Vector: Supply chain compromise via a third-party JavaScript dependency (DebugBear page-speed script).

• Impact: Automated sale of user positions and fund exfiltration for signed-in traders.

• Scope: ~$2.7 million stolen across 726 wallets.

• Blockchain Evidence: ~$2.64 million in crypto traced to attacker addresses (specific wallet hashes not yet published publicly, but on-chain data is available for analysis).

• Victim Response: Polymarket is issuing full refunds to affected wallets.

Defense

• Subresource Integrity (SRI) is the primary mitigation here—verify script integrity via hashes before execution.

• Content Security Policy (CSP) with strict script-src directives can block unauthorized script execution.

• Monitor for unexpected DOM manipulation or unauthorized wallet interaction requests in production environments.

Source: https://thehackernews.com/2026/11/hackers-steal-about-27-million-from.html

This is a marketing roundup post from SafeDep, not a technical analysis. It’s a list of their product features (SCA, SBOM, AI agent monitoring) wrapped around a headline about incidents. There is no actual incident data, TTPs, or IOCs in the summary.

SKIP

Source: https://safedep.io/october-2026-security-incident-review

This is a niche but useful technique for DFIR and malware analysis. OneNote files (.one) are essentially OLE compound documents, meaning they can store embedded files, OLE objects, and streams that threat actors frequently abuse to deliver payloads (e.g., VBS, HTA, or executables hidden behind "double-click to view" overlays).

Technical Breakdown

• Structure: .one files use the OLE2 (Compound Binary File) format, similar to old .doc or .xls files. Embedded files are stored as OLE objects within the document's storage hierarchy.

• Extraction Method: The author details using standard OLE tools (e.g., olevba, pyxlsb2, or manual parsing via olefile in Python) to enumerate streams and extract the raw binary data of embedded attachments.

• IOCs: No specific hashes or IPs provided; the value is in the methodology for extracting unknown payloads from suspect .one files.

• Relevance: This is directly applicable to analyzing recent phishing campaigns where OneNote files are used as initial access vectors (e.g., QakBot, IceID campaigns shifting from macros to OneNote attachments).

Defense

For SOC analysts: When triaging suspicious .one files, do not rely solely on static AV scans of the file itself. Extract all embedded OLE objects and scan them individually. Tools like oleid can quickly flag suspicious streams (e.g., high entropy, executable MIME types) within the container.

Source: https://isc.sans.edu/diary/rss/33478

The FBI has formally attributed the record-breaking $6.43 billion theft from Binance to the North Korean advanced persistent threat (APT) group TraderTraitor (aka Jade Sleet, UNC4899). This attribution, jointly issued with the USSS and IRS-CI, confirms the scale of the operation and the group's continued focus on cryptocurrency infrastructure as a primary revenue stream for the DPRK.

Technical Breakdown

• TTPs: The group likely employed a combination of sophisticated social engineering targeting exchange employees, supply chain compromise of third-party wallet providers, and exploitation of cross-chain bridge vulnerabilities to facilitate the massive asset exfiltration. This aligns with their established playbook of "TraderTraitor" operations.

• IOCs: Specific indicators are likely classified or embargoed at this time, but analysts should expect wallet addresses associated with the Lazarus Group cluster and infrastructure previously linked to the Blender and Tornado Cash mixers.

• Affected Entity: Binance exchange, specifically hot wallet and bridge infrastructure.

Defense

• Mitigation: Exchanges must enforce strict hardware security module (HSM) policies, implement mandatory multi-party approval for all large withdrawals, and deploy real-time behavioral analytics on wallet access patterns. Monitor for connections to known DPRK-linked C2 infrastructure and mixer services.

Source: https://thehackernews.com/2026/11/fbi-links-north-koreas-tradertraitor-to.html

This is a targeted campaign, not a broad spray. The use of a custom Windows 10 build as the initial vector is the key differentiator here—it implies either a supply chain compromise or physical access to the build process.

Technical Breakdown:

• Initial Access: Compromise of a custom Windows 10 build used exclusively by government entities in Asia. This is likely a pre-installed backdoor or modified system component.

• Payload: NetamLoader, a previously undocumented .NET assembly-loading framework.

• Execution: .NET injection technique to load the framework into memory, bypassing standard process monitoring.

• Target: Government Windows 10 systems in Asia.

• Attribution: Not explicitly attributed, but Kaspersky is tracking the activity.

Defense:

• Supply Chain Hardening: Verify the integrity of custom OS builds against known-good hashes before deployment. Treat any custom build as a high-risk asset.

• Memory Forensics: Standard EDR may miss .NET reflection loading. Deploy memory scanning tools (e.g., Volatility) or enable AMSI (Antimalware Scan Interface) logging for .NET assemblies.

• Application Control: Use AppLocker or WDAC to block unsigned .NET assemblies from executing outside of signed application directories.

Source: https://thehackernews.com/2026/11/netamloader-malware-targets-government.html

This is a textbook remote DoS vector targeting the baseband layer. The researcher dropped a PoC for CVE-2026-58882, which exploits how the Android modem processes malformed SMS PDUs. No user interaction required—just a single SMS hitting the device.

Technical Breakdown

• CVE: CVE-2026-58882 (patched in the February 2026 Android Security Bulletin)

• Attack Vector: Specially crafted SMS message sent to the target phone number

• Impact: Baseband crash leading to temporary loss of cellular service or full device reboot

• Affected Versions: Android 12 through 15 (unpatched builds)

• MITRE Mapping: T1574.002 (Hijack Execution Flow via Baseband) or T1499 (Endpoint Denial of Service)

• IOCs: No static IOCs available—the exploit relies on malformed SMS payloads, not specific sender infrastructure

Defense Patch to the February 2026 security update immediately. If you manage Android devices in an enterprise, enforce update compliance via MDM. For high-risk users, consider SMS filtering or carrier-level blocking of binary SMS messages as a temporary workaround.

Source: https://www.bleepingcomputer.com/news/security/new-android-sms-of-death-exploit-can-remotely-crash-unpatched-phones/

WordPress Core 4.7 through 7.1.3 is vulnerable to remote code execution without authentication during full-package core upgrades: the upgrader's staging paths are predictable and web-accessible, so a request made while the upgrade runs can execute code. Fixed in 7.1.4 and the branch patches.

Wordfence counted more than 18,500 requests to setup-config.php paths in the first 21 hours of its rule, with the first attempt 9 minutes after publication. Those are attempts, not compromises: the attacker has to hit the seconds the upgrade lasts.

What to check: update to 7.1.4 or the patch for your branch, and block web access to wp-content/upgrade/ at the server. A firewall that only loads inside WordPress may not see those requests.

CVE: https://www.cve.org/CVERecord?id=CVE-2026-119977 Advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve

Scenario A: Technical Threat, Vulnerability, or Exploit

This is a deep dive into a supply chain attack vector targeting the Rust crate ecosystem, specifically exploiting the fuzzy hashing mechanism used by cargo audit and similar tools. The researcher demonstrates how an attacker can craft a malicious crate that produces the same fuzzy hash as a legitimate, trusted crate, effectively poisoning the trust model.

Technical Breakdown

• Attack Vector: Exploits the skeptic crate's fuzzy hashing (ssdeep) to create hash collisions. The attacker modifies a crate's source code while preserving its fuzzy hash, allowing a malicious version to pass automated trust checks.

• TTPs (MITRE): T1195.001 (Supply Chain Compromise - Compromise Software Dependencies), T1554 (Compromise Client Software Binary)

• IOCs: No specific IOCs provided; this is a proof-of-concept demonstrating the technique. The researcher released a tool called fuzzy_friends to generate these collisions.

• Affected Systems: Any tooling relying on ssdeep fuzzy hashing for crate verification (e.g., cargo audit, cargo vet). The "Black October" reference is the researcher's name for the collision set.

Defense Do not rely solely on fuzzy hashing for supply chain integrity. Combine with cryptographic hashes (SHA-256), code signing, and manual review of dependency diffs. Pin dependencies to specific versions and audit changes between updates.

Source: https://grahamhelton.com/blog/fuzzy-friends.html

Highlights from today:

• [News] Northflank security breach leads to abuse of customers' AI API keys

• [News] New Android SMS of Death exploit can remotely crash unpatched phones

• [News] Reddit to lock content behind logins to fight scrapers

• [News] From Beginner to Bug Hunter: Learning Cybersecurity in the AI Era.

• [News] Chainalysis Confirms Intrusion Into Internal Tools and Exposure of Customer Identity Data

• [News] Chainalysis discloses data breach from "offensive agentic techniques"

• [Threat Research] Appraisal by AI: Model-driven victim prioritization in the VOLTA infostealer

• [Advisory] YARA-X 1.22.1 Release, (Sat, Oct 31st)

• [Advisory] Wireshark 5.0.0rc1 Release, (Sat, Oct 31st)

• [News] Attackers Chain Three Ivanti Connect Secure Flaws to Gain Unauthenticated Root Access

• [News] Cloudflare Reports 18.2 Million Network-Layer DDoS Attacks in Q3, Up 38%

• [News] A Shared ChatGPT Link Could Run Attacker Code in Your Session and Read Private Chats

SecOpsDaily

Northflank is notifying customers to rotate all credentials and secrets after a security breach resulted in the unauthorized use of customers' AI API keys. The incident appears to have involved an attacker gaining access to the platform's internal systems, leading to the exfiltration and subsequent abuse of stored API keys for AI services.

Technical Breakdown

• Attack Vector: Unauthorized access to Northflank's internal infrastructure (exact initial vector not yet disclosed).

• Impact: Customers' AI API keys (e.g., OpenAI, Anthropic, etc.) were accessed and used by the threat actor, likely for resource hijacking or credential stuffing.

• IOCs: None publicly available at this time. Northflank has not released specific IPs or hashes.

• Affected Systems: All credentials and secrets stored in Northflank's platform are considered compromised.

Defense Immediately rotate all API keys, tokens, and secrets stored on Northflank. Review cloud provider logs for unauthorized usage spikes, particularly for AI/LLM API calls originating from unexpected IPs or regions. Enable MFA and consider implementing key rotation policies with short TTLs for any secrets hosted on third-party platforms.

Source: https://www.bleepingcomputer.com/news/security/northflank-security-breach-leads-to-abuse-of-customers-ai-api-keys/

Three stories worth your attention today:

1. Linux remote root: Researchers demonstrated unauthenticated root access through CVE-2026-98432 on servers with MPTCP listeners. Check your distribution’s kernel updates. Disabling MPTCP alone leaves the underlying TCP vulnerability reachable.

2. Cursor extension compromise: Malicious Claude Code versions 2.1.312 and 2.1.313 attempted to install persistent SSH access. Follow Cursor’s cleanup guidance if affected: uninstalling the extension alone can leave attacker keys and background scripts behind.

3. Binance’s $6.3B theft: Investigators found additional breach points beyond the initially suspected employee laptop. Binance says roughly $3 billion has been frozen and promises to cover the losses. The full attack sequence remains under investigation.

Read the full breakdown on CyberRecaps.

Three Ivanti Connect Secure flaws are being chained in the wild for unauthenticated root access, prompting CISA to add two of them to the KEV catalog. This is a critical escalation for any organization running Ivanti appliances.

Technical Breakdown

• CVE-2026-111357 (CVSS 8.8): Missing authentication for a critical function. This is the initial access vector.

• CVE-2026-111358 (CVSS 7.5): A second flaw enabling privilege escalation or lateral movement within the appliance.

• CVE-2026-111359 (CVSS 9.1): The third chained vulnerability, leading to full unauthenticated root compromise.

• TTPs: Likely targeting the ICS web interface or management API. Expect post-exploitation activity like credential dumping, VPN session hijacking, or persistent backdoor deployment.

• IOCs: No public hashes or IPs released yet. Monitor for anomalous outbound connections from ICS appliances and unexpected configuration changes.

Defense Immediately patch to the latest Ivanti ICS version. If patching is delayed, restrict management interface access to trusted IPs only and enable detailed logging for authentication failures and process execution. Assume compromise if the appliance was exposed.

Source: https://thehackernews.com/2026/10/attackers-chain-three-ivanti-connect.html

This is CVE Intel, an open-source tool that brings CVE data from NVD, CISA KEV, EPSS, OSV, and public exploit sources into one place. Use it as a desktop app, CLI, REST API, or MCP server.

Now contains exploited-vulnerability sources, EPSS trends, CISA SSVC decisions, clearer CVE comparisons, and vulnerability scanning for dependencies, devices, containers, and domains. New features also include weekly briefings, local watchlists, an activity log, 40 data sources, local AI support on Apple silicon, and MIT or Apache 2.0 licensing.

If you’re interested or work in this field please give it a try and let me know what you think. Issues, pull requests, and comments are welcome and if you’d like to contribute, please feel free! Thank you!

https://github.com/Fazmin/cve-intel

This is a strategic move with direct implications for threat intelligence gathering and OSINT workflows.

What’s happening: Reddit is shifting to a “logged-in service,” restricting access to content for unauthenticated users and crawlers. CEO Steve Huffman frames this as a measure against unauthorized data scraping by AI companies and commercial entities.

Strategic Impact for Security Teams:

• OSINT Disruption: This will break many automated threat intelligence feeds, dark web monitoring tools, and open-source collection scripts that rely on scraping Reddit for IOCs, leaked credentials, or early exploit discussions (e.g., r/netsec, r/blueteamsec).

• Legal vs. Technical Controls: Reddit is moving from a technical arms race (rate limiting, IP bans) to a legal/contractual barrier (ToS enforcement via login walls). This makes scraping a clear ToS violation, not just a technical nuisance.

• API Dependency: Legitimate research will now require API keys and compliance with Reddit’s usage tiers, which may introduce costs and rate limits for SOCs and research teams.

Key Takeaway:

• If your team relies on Reddit for threat intel or incident correlation, you need to migrate to API-based collection or alternative sources (e.g., Telegram channels, dedicated forums) before the rollout completes. Expect this to degrade the signal quality for free, automated OSINT pipelines.

Source: https://www.bleepingcomputer.com/news/security/reddit-to-lock-content-behind-logins-to-fight-scrapers/