Search: “assembly code”

7 stories

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Malware 239 Vulnerability 150 Ransomware 61 Exploit / PoC 49 Threat actor 47 Data breach 26 Policy & legal 23 Phishing & fraud 16 Industry 15 Research 12 Advisory 5 Tools 4

SeverityAll critical 196 high 226 medium 171 low 47 info 7

SEMA-GUARD: Semantic and Graph-Based Vulnerability Detection in Assembly Code

SEMA-GUARD uses semantic analysis and graph neural networks to detect vulnerabilities in assembly code, achieving 85.1% accuracy on a Juliet-derived benchmark.

SEMA-GUARD is a framework that detects vulnerabilities in compiled programs when source code is unavailable, targeting malware, firmware, and embedded systems analysis. It enriches control flow graphs with low-level execution semantics including stack manipulations, memory accesses, and data flow. Evaluated on a Juliet Test Suite set compiled to assembly and split into function-level chunks, it achieves 85.1% accuracy and an F1 score of 0.801, outperforming purely statistical or structural approaches.

arXiv cs.CRSep 15, 14:35 UTC · 1d agoResearch1

EU's Cyber Resilience Act starts the 24-hour vulnerability clock

EU Cyber Resilience Act reporting rules take effect, requiring manufacturers to disclose actively exploited vulnerabilities to ENISA within 24 hours, with fines reaching €15 million.

The Cyber Resilience Act's Article 14 mandatory reporting duties became applicable, requiring makers of products with digital elements sold in the EU — regardless of where they are based — to file an early warning within 24 hours of becoming aware of an actively exploited vulnerability, a detailed notification within 72 hours, and a final report within 14 days of releasing a fix. Reports must be submitted through ENISA's Single Reporting Platform to the designated CSIRT, and non-compliance with these core duties can trigger fines up to €15 million or 2.5 percent of annual turnover. Manufacturers must also inform affected users of available fixes without undue delay, and most remaining CRA provisions, including mandatory SBOMs and security-by-design requirements, become applicable on December 11, 2027.

The Register · SecuritySep 11, 11:34 UTC · 5d agoPolicy & legal

AD Rights Management Service (Part 2): Extraction, Offline Decryption, and the Unrotatable Key

Huntress research shows AD RMS SLC root key is unrotatable and never expires, so its compromise permanently exposes all RMS-protected documents.

Part 2 of Huntress's AD RMS series details server-side attacks: extracting the Server Licensor Certificate (SLC) private key and performing offline decryption of protected documents. The SLC key has no expiry or rotation mechanism, with a 255-year certificate validity (2002–2258), so whoever recovers it can decrypt every document the deployment ever protected, indefinitely. The author released SharpRMS, a unified tool combining the 2016 DisARMS client-side attacks with new server-side key extraction and decryption capabilities. The research frames the SLC as comparable to KRBTGT and the DPAPI domain backup key, though not equivalent to domain compromise.

HuntressSep 10, 04:00 UTC · 6d agoResearch

Building a Linux GPU Driver for the M4 Mac Mini in One Month

Two developers built a fully OpenGL ES 3.0 compliant Linux GPU driver for the M4 Mac Mini in one month via clean-room reverse engineering.

Niklas and the author reverse engineered Apple's AGX GPU firmware ABI and user-space components in about a month, a process that normally takes years, producing an OpenGL ES 3.0 conformant driver fast enough to run Minecraft at 200fps on an M4 Mac Mini. The work was done transparently using hypervisor traces without examining Apple binaries, following clean-room practices, and included a custom shader compiler, command stream builder, and a full Linux kernel driver for the firmware ABI. The A18 Pro firmware ABI proved significantly more complex than the M1's, with 1.5x as many structs and twice as many pointers. All experiments and provenance evidence were published in public agx-re repositories.

Hacker News · AISep 15, 19:30 UTC · 1d agoResearch HN 40↑ · 5 comments

Learn How to Build Security Operations Ready for AI

Wiz sponsors a webinar on building AI-ready security operations, focusing on attack-path visibility, exposure prioritization, and faster detection-to-remediation workflows.

A contributed piece promotes next week's Wiz webinar, How to Build AI Threat Readiness Across Your Security Operations, featuring a Wiz expert. The session covers using unified security context to separate urgent exposures from noise, understand attack paths across cloud, code, identities, SaaS, and AI services, and connect validated risks to remediation owners.

The Hacker NewsAug 27, 11:56 UTC · 20d agoIndustry

Exaforce extends its AI security tool to monitor more than just Claude

Exaforce AI Security extends beyond Claude to monitor OpenAI, Gemini, and Copilot agents using existing SOC telemetry, no new endpoint agents.

Exaforce expanded its June Claude Compliance API integration into Exaforce AI Security, adding monitoring for OpenAI, Gemini, Microsoft Copilot, and OAuth-connected AI apps. The tool inventories AI agents by correlating EDR, cloud, SaaS, and model-provider logs without new gateways or endpoint agents, and can respond by revoking sessions, deactivating API keys, isolating devices, or killing agent processes via existing controls. Analysts note the agentless approach lowers friction but lacks runtime inspection and inline blocking offered by competitors such as Palo Alto Prisma AIRS, SentinelOne Prompt AI Agent Security, and CrowdStrike Falcon Guardian. A March 2026 Cloud Security Alliance survey found 68% of organizations cannot distinguish human from AI-agent activity and 74% report AI agents receive excessive access.

CSO OnlineSep 15, 13:00 UTC · 1d agoTools

Triage & Response Bottlenecks Eating into MSSP Margins: How to Remove the Friction

ANY.RUN says manual triage bottlenecks erode MSSP margins and promotes its Threat Intelligence Lookup and sandbox to cut Tier 1 workload by up to 20%.

Vendor blog post from ANY.RUN describes recurring MSSP triage and response bottlenecks: manual alert validation, unnecessary Tier 2 escalations, manual handoffs, outdated threat data, and disconnected tools. It cites a healthcare MSSP case study where the Tier 1 closure rate rose from 20% to 70% and false escalations dropped 34% after adopting its tools. The piece claims ANY.RUN can reduce Tier 1 workload by up to 20%, letting MSSPs absorb more clients without proportional headcount growth.

ANY.RUNSep 2, 07:18 UTC · 14d agoIndustry