Industry Category

Computer Software/Engineering

Breach intelligence, attack campaigns, and threat reports targeting the Computer Software/Engineering sector.

2541 threat reports
Page 3 of 212
Explore Other Sectors
AccountingAerospaceAerospace/AviationAgricultureAirlines/AviationAnimationApparel/FashionArchitecture/PlanningArtificial IntelligenceArtificial Intelligence/Machine LearningArts/CraftsAutomotiveAviation/AerospaceBanking/MortgageBiotechnology/GreentechBlockchain/CryptocurrencyBroadcast MediaBroadcasting MediaBroadcasting/MediaBuilding MaterialsBusiness Supplies/EquipmentCapital Markets/Hedge Fund/Private EquityChemicalChemicalsCivic/Social OrganizationCivil EngineeringCloud ComputingCloud Computing/SaaSCloud Native Security Fabric (CNSF)Cloud ServicesCommercial FacilitiesCommercial Real EstateComputer GamesComputer HardwareComputer NetworkingComputer Software/EngineeringComputer/Network SecurityConstructionConsultingConsumer ElectronicsConsumer GoodsConsumer ServicesCosmeticsCosmeticsCritical ManufacturingCryptocurrenciesCryptocurrencyCustomer ServicesCybersecurityDairyDating/Personal ServicesDating/Social PlatformsDefense/SpaceDesignE-LearningEducation ManagementElectrical/Electronic ManufacturingEmergency ServicesEnergyEnergy/Oil/Solar/GreentechEntertainment/Movie ProductionEnvironmental ServicesEvents ServicesExecutive OfficeFacilities ServicesFarmingFashion/ApparelFinancial ServicesFine ArtFisheryFood ProductionFood/BeveragesFortune 500 companiesFranchisingFundraisingGambling/CasinosGamingGaming/CasinosGovernment AdministrationGovernment FacilitiesGovernment RelationsGraphic Design/Web DesignHealth Care / Life SciencesHealthcareHigher Education/AcadamiaHospitalityHospitalsHuman Resources/HRImport/ExportIndividual/Family ServicesIndustrial AutomationInformation ServicesInformation Technology/ITInsuranceInternational AffairsInternational Trade/DevelopmentInternetInvestment Banking/VentureInvestment Management/Hedge Fund/Private EquityJudicialJudiciaryLaw EnforcementLaw Practice/Law FirmsLegal ServicesLegislative OfficeLeisure/TravelLogistics/ProcurementLuxury Goods/JewelryMachineryManagement ConsultingManufacturingMaritimeMarket ResearchMarketing/Advertising/SalesMechanical or Industrial EngineeringMedia ProductionMedical EquipmentMedical PracticeMilitary IndustryMining/MetalsMobileMuseums/InstitutionsMusicNewspapers/JournalismNon-Profit/VolunteeringOil/Energy/Solar/GreentechOnline PublishingOther IndustryOutsourcing/OffshoringPackage/Freight DeliveryParkingPharmaceuticalsPhilanthropyPhotographyPlasticsPolitical OrganizationPrimary/Secondary EducationProfessional ServicesProfessional TrainingPublic Relations/PRPublic SafetyPublishing IndustryRailroad ManufactureReal Estate/MortgageRecreational Facilities/ServicesReligious InstitutionsRenewables/EnvironmentResearch IndustryRestaurantsRetail IndustryRoboticsRural HealthcareSecurity/InvestigationsSemiconductorsShipbuildingSocial Media/InternetSporting GoodsSportsStaffing/RecruitingSupermarketsTechnologyTechnology/ITTelecommunicationsThink TanksToys and GamesTransportationTravel/TourismTrucking/FreightUtilitiesVenture Capital/VCWarehousingWater and Waste ManagementWater and WastewaterWater and Wastewater SystemsWater and Wastewater TreatmentWater TreatmentWater, Waste, Steam, and Air Conditioning ServicesWater/Waste ManagementWater/WastewaterWater/Wastewater ManagementWater/Wastewater/UtilitiesWholesaleWine/SpiritsWirelessWriting/Editing

Computer Software/Engineering Threat Reports

Showing 25–36 / 2541 reports
Trojanized Claude Code Extension: How a Single Cursor Marketplace Update Backdoored 5,000 Developer Machines
Trojanized Claude Code Extension: How a Single Cursor Marketplace Update Backdoored 5,000 Developer Machines

Trojanized Claude Code Extension: How a Single Cursor Marketplace Update Backdoored 5,000 Developer Machines

On October 29, 2026, a trojanized version of Anthropic's official Claude Code extension (version 2.1.313) was distributed through Cursor's IDE marketplace under the legitimate publisher identity anthropic.claude-code. Between approximately 2:27 a.m. and 1:35 p.m. PT, up to 5,000 developers auto-updated to the malicious build, which injected a 66-line JavaScript loader to plant an attacker-controlled SSH key labeled "svc-telemetry," establish a reverse tunnel to 134.209.82.225, install cross-platform persistence, and beacon host reconnaissance data—including environment variable names referencing cloud credentials—over unencrypted HTTP to port 8099. This incident reflects a sharp escalation in software supply-chain attacks targeting AI developer tooling. As agentic AI extensions gain privileged access to developer workstations and cloud credential stores, attackers are exploiting marketplace trust relationships and auto-update mechanisms to achieve persistent footholds at the earliest stage of the software development lifecycle, compressing the window between initial compromise and credential exposure.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
AI Is Now a Standard Weapon in North Korea's Cyber Arsenal—Here's What That Means for Your Cloud
AI Is Now a Standard Weapon in North Korea's Cyber Arsenal—Here's What That Means for Your Cloud

AI Is Now a Standard Weapon in North Korea's Cyber Arsenal—Here's What That Means for Your Cloud

Throughout 2026, Microsoft Threat Intelligence documented North Korean state-sponsored threat actors—including Jade Sleet, Coral Sleet, Onyx Sleet, Diamond Sleet, Sapphire Sleet, Pearl Sleet, Jasper Sleet, and Emerald Sleet—systematically embedding generative and agentic AI into every phase of their attack chains. AI accelerated reconnaissance, mass-produced spear-phishing lures (Onyx Sleet generated dozens of tailored PDF decoys within minutes), enabled supply-chain trojans built with AI-assisted development platforms, and supported large-scale fraudulent IT worker schemes. Jade Sleet launched campaigns across three fabricated front companies in a single week, while Sapphire Sleet likely used AI during an August 2026 Rust software supply-chain compromise. The operations advance regime goals: cryptocurrency theft, strategic intelligence collection, and sanctions evasion. This report signals a structural inflection point: AI is no longer an experimental add-on for nation-state actors—it is an operationalized force multiplier. Defenders face AI-generated lures, AI-accelerated retooling, and agentic penetration-testing frameworks (ARTEX) deployed in live operations, demanding equally automated, cloud-native defensive architectures to keep pace.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(medium)
Read report
Hugging Face GPU Hijack: How a Malicious AI Model Campaign Stole Cloud Compute at Scale
Hugging Face GPU Hijack: How a Malicious AI Model Campaign Stole Cloud Compute at Scale

Hugging Face GPU Hijack: How a Malicious AI Model Campaign Stole Cloud Compute at Scale

In late October 2026, researchers at Pluto Security uncovered a recurring supply-chain campaign on Hugging Face in which a financially motivated, Chinese-speaking threat actor published 31 malicious AI model repositories across seven accounts in two coordinated waves since September 2026. The models, disguised as Qwen2 test checkpoints, exploited Hugging Face's trust_remote_code feature to execute malicious Python code at model-load time on GPU inference servers. The most downloaded model, MENXIANGYU/qwen2-tiny, accumulated 28,412 downloads, silently installed a cryptocurrency miner, established persistence, and opened reverse shells granting direct server access. The attacker's wallet collected roughly $5,000 in Pearl (PRL) cryptocurrency, and a second wave of repositories reappeared within days of the initial takedown—one introducing a container-escape script. Traditional AV and partner scanning tools returned clean results throughout the campaign. This incident signals a maturing threat pattern in which adversaries weaponize trusted AI model repositories as a software supply-chain vector, bypassing conventional security controls by abusing legitimate platform features rather than known malware signatures. As enterprises accelerate AI workload adoption on GPU-intensive cloud infrastructure, the attack surface for model-based supply-chain compromise is expanding rapidly, demanding new runtime enforcement and egress control strategies.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
GhostAction 2026: How a GitHub Actions Supply-Chain Campaign Targeted Developer Credentials and Cloud Access
GhostAction 2026: How a GitHub Actions Supply-Chain Campaign Targeted Developer Credentials and Cloud Access

GhostAction 2026: How a GitHub Actions Supply-Chain Campaign Targeted Developer Credentials and Cloud Access

Between October 8 and 26, 2026, the GhostAction supply-chain campaign injected malicious GitHub Actions workflow files into more than 23,000 public repositories using roughly 1,800 compromised developer accounts, pushing 72,000 commits across two escalating waves. Payloads targeted repository secrets, AWS OIDC tokens, and AI-provider API keys, while a PolinRider-derived 'font stealer' attempted to install a Node.js credential stealer on local developer machines. GitHub's platform controls blocked workflow execution, and GitGuardian found no confirmed successful runs, but stolen tokens from the October 8 wave remained active weeks later, demonstrating persistent unauthorized access across CI/CD and cloud environments. The incident illustrates how adversaries are weaponizing developer trust in automation pipelines to harvest cloud credentials at scale. With attackers now probing AWS OIDC federation and AI-API keys alongside traditional repository secrets, the attack surface extends well beyond source code into live cloud workloads—making CI/CD hygiene, token lifecycle management, and cloud egress controls a board-level priority.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
The AI Relay in Your Dev Pipeline: How a Shadow Service Hijacked Codex and Claude Code at a Dozen Enterprises
The AI Relay in Your Dev Pipeline: How a Shadow Service Hijacked Codex and Claude Code at a Dozen Enterprises

The AI Relay in Your Dev Pipeline: How a Shadow Service Hijacked Codex and Claude Code at a Dozen Enterprises

In late October 2026, Symantec's Threat Hunter Team exposed a clandestine relay service that had been silently installing authentic OpenAI Codex and Anthropic Claude Code CLI tools across enterprise environments in mainland China, South Korea, Taiwan, and Malaysia since early 2026. The service routes all AI agent traffic through attacker-controlled relay infrastructure, disables execution sandboxes, enables unrestricted network access for write operations, suppresses telemetry, and replaces corporate API credentials with relay-issued tokens. At least a dozen organizations were confirmed affected, none knowingly. The relay operator gains full visibility into every prompt, file, and secret transiting the agent, and can silently alter or fabricate every model response returned to the user. This incident crystallizes the emerging shadow AI threat class: employees bypassing geographic or procurement controls introduce unauthorized AI relay infrastructure that operates with the full privileges of a developer account. As agentic AI coding tools become core to software delivery pipelines, a single compromised relay can silently manipulate code, harvest secrets, and pivot across cloud workloads—making egress policy enforcement and supply-chain visibility critical board-level concerns heading into 2027.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
CVSS 10.0 GitLab RCE (CVE-2026-97229): How a Ruby Dependency Gap Left Alpine Linux Exposed After Patching
CVSS 10.0 GitLab RCE (CVE-2026-97229): How a Ruby Dependency Gap Left Alpine Linux Exposed After Patching

CVSS 10.0 GitLab RCE (CVE-2026-97229): How a Ruby Dependency Gap Left Alpine Linux Exposed After Patching

In October 2026, a threat actor attempted to exploit CVE-2026-97229, a CVSS 10.0 remote code execution vulnerability in GitLab's Ruby-based CI/CD regex compiler (Onigmo engine), targeting Alpine Linux's self-hosted GitLab server. The attacker registered a new account on October 20, submitted crafted CI configurations, and crashed GitLab worker processes eight times over two days. Alpine had upgraded to GitLab 19.3.6 on October 22 but remained vulnerable because its server used standard Alpine Ruby rather than GitLab's bundled patched Ruby. No confirmed code execution was found, but Alpine rebuilt the server from scratch, rotated all secrets, and reset all passwords after acknowledging that a successful exploit would leave no detectable trace in logs. This incident underscores a growing gap in supply-chain patch coverage: organizations running GitLab on self-compiled or distribution-packaged Ruby installations may believe they are patched after a GitLab upgrade, while the underlying runtime dependency remains exploitable. As proof-of-concept exploit code is already public (Rapid7, October 13, 2026), any unpatched self-managed GitLab instance—especially those permitting open user registration—faces elevated and immediate risk.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(low)
C&CCommand & Control(low)
EExfiltration(low)
IImpact(high)
Read report
26,400 Live Cloud and AI API Keys Found in Public Gitee Repositories — What Enterprises Must Do Now
26,400 Live Cloud and AI API Keys Found in Public Gitee Repositories — What Enterprises Must Do Now

26,400 Live Cloud and AI API Keys Found in Public Gitee Repositories — What Enterprises Must Do Now

In October 2026, independent researcher Ben Zimmermann published findings from a month-long scan of 7.25 million public Gitee repositories, uncovering 26,400 valid, live credentials for cloud and AI services. Using TruffleHog and Kingfisher scanners against full commit histories, he confirmed active keys for Alibaba Cloud, DeepSeek, OpenAI, YouTube API, Zhipu BigModel, AWS, GitHub, and Google Cloud. One credential was an active organization-admin key for a major enterprise AI platform. Vendors were notified, but no confirmation of revocation was received before publication, leaving any organization with keys in public Gitee history at immediate risk of account takeover, quota abuse, unexpected charges, and unauthorized data access. This incident underscores a dangerous acceleration in AI-era credential sprawl: as developers rapidly integrate cloud and AI APIs, secret hygiene practices are not keeping pace. With nearly half of exposed credentials dated to 2025 alone, the attack surface is expanding in real time, and a single leaked organization-admin key can grant adversaries deep access to enterprise AI infrastructure.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(high)
Read report
Yoba 2026: How Fake AI Apps Used Signed Executables to Mine Crypto Undetected
Yoba 2026: How Fake AI Apps Used Signed Executables to Mine Crypto Undetected

Yoba 2026: How Fake AI Apps Used Signed Executables to Mine Crypto Undetected

Beginning in July 2026, threat actors launched a campaign dubbed 'Yoba' that distributed trojanized desktop applications impersonating OpenAI ChatGPT and Anthropic Claude tools via fake GitHub repositories. Attackers used DLL sideloading against legitimate, digitally signed OpenAI Codex and Claude executables to deploy a multi-stage malware chain—YobaDropper then YobaLoader—ultimately injecting an XMRig cryptocurrency miner into svchost.exe. Command-and-control infrastructure relied on a Telegram-seeded domain generation algorithm and Google DNS-over-HTTPS to evade traditional network monitoring, effectively hijacking victim compute resources for Monero mining while evading most endpoint and gateway defenses. The Yoba campaign reflects a rapidly maturing attacker playbook: exploiting surging enterprise and consumer interest in AI tools to socially engineer downloads, while layering DLL sideloading, DGA-based C2, and geo-fencing anti-analysis tricks to extend dwell time. As AI application adoption accelerates across industries, defenders face an expanding attack surface where trusted brand names and code-signing status can no longer serve as reliable trust signals.

Medium impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(high)
Read report
Inside Claude's Sandbox: How a Researcher Turned AI Prompts into Cloud Credential Theft
Inside Claude's Sandbox: How a Researcher Turned AI Prompts into Cloud Credential Theft

Inside Claude's Sandbox: How a Researcher Turned AI Prompts into Cloud Credential Theft

In a controlled research exercise published by Bishop Fox, security researcher Chris Davis systematically probed the sandbox environment surrounding Anthropic's Claude AI model, uncovering a chain of exposures spanning container internals, process memory, and live authorization tokens. Beginning with seemingly benign queries about the sandbox's operating environment, Davis was able to extract sensitive runtime artifacts that Claude surfaced during interaction. The investigation revealed that the model's execution context lacked adequate isolation controls, enabling an adversary to pivot from conversational access to credential harvesting—demonstrating a complete kill chain from initial prompt to exfiltration of bearer tokens usable against downstream cloud services. This research arrives as enterprises accelerate GenAI adoption with insufficient runtime security controls. Agentic AI deployments, where models autonomously call APIs and access internal systems, dramatically expand the attack surface. Security teams now face a new class of threat: sandbox escapes and token exfiltration via AI interaction rather than traditional exploit code.

Medium impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(low)
Read report
Cybersecurity Black Week 2026: Five Critical Incidents, One Week, Zero Margin for Error
Cybersecurity Black Week 2026: Five Critical Incidents, One Week, Zero Margin for Error

Cybersecurity Black Week 2026: Five Critical Incidents, One Week, Zero Margin for Error

During the week of October 19–25, 2026, security teams faced an unprecedented convergence of critical vulnerabilities dubbed 'Cybersecurity Black Week.' Five major incidents struck simultaneously: two unauthenticated RCE flaws in PHP (CVE-2026-109618/109619, CVSS 9.2), a supply-chain compromise of LiteLLM's PyPI release pipeline, unpatched Linux kernel KSMBD RCE vulnerabilities disclosed prematurely to public mailing lists, a CVSS 10.0 integer-overflow in GitLab (CVE-2026-110264), a Brotli decoder RCE in Node.js (CVE-2026-111497), and a compromised certificate authority chain (eMudhra/emSign) enabling MITM attacks against Python package infrastructure. Each incident demanded a distinct remediation posture—emergency patching, full environment rebuilds, credential rotation, and certificate trust-store replacement—overwhelming security and operations teams simultaneously. This cluster of incidents illustrates an accelerating trend: AI-assisted vulnerability discovery, supply-chain infiltration of developer toolchains, and coordinated disclosure failures are compressing defender response windows to hours. Organizations relying on patch-centric security strategies are increasingly exposed during the gap between public disclosure and full remediation across heterogeneous environments.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(high)
Read report
ESET APT Report Q2–Q3 2026: How China, Iran, North Korea, and Russia Are Reshaping the Threat Landscape
ESET APT Report Q2–Q3 2026: How China, Iran, North Korea, and Russia Are Reshaping the Threat Landscape

ESET APT Report Q2–Q3 2026: How China, Iran, North Korea, and Russia Are Reshaping the Threat Landscape

Between April and September 2026, ESET researchers documented an expansive wave of APT activity spanning China-, Iran-, North Korea-, Russia-, and Belarus-aligned threat actors. China-aligned groups pursued semiconductor espionage in Taiwan and fraud-linked intelligence collection across Southeast Asia and Oceania. Iran-aligned actors including FilthyFeline and MuddyWater resumed operations against Israeli and US targets after a period of reduced activity. North Korea's Lazarus Group expanded into drone-sector espionage tied to the Russia-Ukraine conflict, while DeceptiveDevelopment pivoted to software supply-chain compromises to harvest developer credentials. Russia-aligned groups continued targeting European defense and government entities, with Belarus-aligned FrostyNeighbor executing the first documented destructive cyberattack by a Belarus-linked actor in the European theater, striking a Ukrainian transportation manufacturer. This reporting period marks a meaningful escalation in APT operational breadth and destructive ambition. The convergence of Russia-Belarus cyber-proxy activity, North Korea's drone-sector targeting, and the widespread adoption of AI-assisted malware development signals a new phase in state-sponsored threat evolution that defenders across critical infrastructure, semiconductors, and financial services must urgently address.

Medium impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
The Shai-Hulud Worm Proves SBOMs Are Not Enough: What Supply Chain Defenders Must Do Now
The Shai-Hulud Worm Proves SBOMs Are Not Enough: What Supply Chain Defenders Must Do Now

The Shai-Hulud Worm Proves SBOMs Are Not Enough: What Supply Chain Defenders Must Do Now

At the ISC2 Security Congress 2026, Atlassian product security manager Deepam Kanjani detailed a real-world supply chain compromise involving the Shai-Hulud worm, a malicious transitive dependency buried three layers deep inside a seemingly legitimate npm package with over 3,400 GitHub stars and a matching SHA hash. Because the dependency was not direct, it evaded top-level SBOM audits and initial behavioral alerts were dismissed as false positives. The team was forced to manually correlate logs across more than 400 services without reliable runtime telemetry, severely hampering incident scoping. Attribution led to dead ends, with the publisher identity fabricated, though later research linked subsequent Shai-Hulud campaigns to threat actor TeamPCP. This incident underscores a widening gap between static dependency inventories and the dynamic reality of production environments. As software supply chain attacks grow in sophistication and frequency, organizations that rely solely on SBOMs for incident scoping face dangerous blind spots in runtime visibility, transitive dependency tracking, and rapid stakeholder communication during active compromise.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(high)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
[ INCIDENT RESPONSE // UNDER ATTACK? ]

Stop Active Cloud Data Exfiltration

Aviatrix Rapid Containment helps teams instantly identify what data is leaving the environment, from which workload, and where it’s going — during an active breach.

Looking for threats in a different sector?

Browse All Threat Reports