Last updated: October 5, 2026 at 10:28 AM UTC
All 897 Vulnerability 362 Breach 144 Threat 384 Defense 7

Compromised joyfill npm packages run a remote access trojan when imported

Attackers published malicious versions of the @joyfill/components and @joyfill/layouts npm packages that run a remote access trojan as soon as the package is imported, not merely installed. Because the payload executes at import time, defenses that block install scripts, such as installing with scripts disabled, do not stop it. The malicious code sat only in the published tarballs with no matching source change, pointing to a registry or publishing pipeline compromise. Once loaded, it profiles the host, opens a remote-control channel, and can run shell commands, upload files, read the clipboard, and tamper with developer tools, using blockchain networks to resolve its next payload for resilience.

Check
Check whether any project, CI runner, or build imported the malicious @joyfill/components or @joyfill/layouts versions, focusing on import-time execution rather than only install scripts.
Affected
Developers and CI pipelines that imported the compromised joyfill packages; the trojan runs in any process that loads them, giving attackers remote control and access to developer credentials and tools.
Fix
Remove the malicious versions, pin known-good releases, rebuild from clean state, rotate secrets reachable from affected machines, and add runtime and egress monitoring, since install-script controls do not catch import-time payloads.

Security scanners can be turned into a foothold for supply chain attacks

New research shows that application security scanners embedded in the software pipeline can themselves be attacked, because analyzing a repository is not always a read-only action. Many scanners execute code or process files in ways that can be forced to run attacker content when it is handled without isolation. For example, a tool that scans cloud configuration files against a folder of custom rules can be fed a rule that is actually a malicious program, which the scanner runs when it loads it. Since scanners often hold broad access to source, secrets, and build systems, a compromised one is a strong pivot point into the wider environment.

Check
Review how your code and configuration scanners handle untrusted repository content, and check whether they execute rules, plugins, or files without sandboxing and multi-tenant isolation.
Affected
Teams whose security scanners process untrusted repository content without isolation; an attacker controlling a scanned repo can plant content that runs code inside the scanner, which often holds broad access to secrets.
Fix
Run scanners in isolated, least-privilege sandboxes, treat all scanned content as untrusted input, enforce multi-tenancy separation, and limit the source, secrets, and build access that scanning environments hold.

Critical Arista VeloCloud Orchestrator flaw exploited in attacks

Arista patched a critical vulnerability in on-premises VeloCloud Orchestrator, the console that configures and manages VeloCloud SD-WAN deployments, that is already being exploited. Tracked as CVE-2026-16812 and scored 10.0, it is an unauthenticated operating-system command injection that lets a remote attacker reach privileged functionality meant only for internal use. Arista warns successful exploitation can compromise the confidentiality, integrity, and availability of the orchestrator and everything it manages. There is no configuration that prevents exposure, since the web interface is reachable by default. CISA added it to its exploited-vulnerabilities catalog. Hosted and Dedicated deployments were fixed before the advisory and are not affected.

Check
Identify on-premises VeloCloud Orchestrator instances, upgrade to the fixed 5.2.3.14, 6.1.3.4, 6.4.2.4, or 7.x releases immediately, and restrict the web interface to trusted administrative networks.
Affected
Organizations running on-premises VeloCloud Orchestrator (CVE-2026-16812); the web interface is exposed by default, needs no credentials, and active exploitation gives attackers command execution over the orchestrator and managed devices.
Fix
Upgrade to the fixed VCO versions, limit web interface access to trusted networks, and review VCO web access logs for unusual path components, encoded characters, or high request rates.

n8n sandbox escape lets workflow editors run commands on the server

n8n patched a high-severity flaw that lets an authenticated user who can create or edit workflows escape the expression sandbox and run operating-system commands as the n8n process. Security Joes found it while probing n8n's February fix for an earlier sandbox bug, and the gap sits in how the rewriter handled a bare identifier in a concise arrow function body. Successful exploitation can expose the n8n encryption key and allow decryption of stored credentials. It is tracked as GHSA-gv7g-jm28-cr3m with a score of 8.7 and no CVE assigned yet. Fixed versions are 2.31.5 and 2.32.1, with no patched 1.x release listed.

Check
Update self-hosted n8n to 2.31.5 or 2.32.1 or later, and treat the vendor's interim advice to restrict editing to trusted users as an incomplete stopgap rather than a fix.
Affected
Self-hosted n8n deployments before 2.31.5 or on 2.32.0 (GHSA-gv7g-jm28-cr3m); any account allowed to create or modify workflows can run commands as the n8n process and expose stored credentials.
Fix
Upgrade to a fixed release, rotate the n8n encryption key and stored credentials if you ran an exposed version, and keep the instance off the public internet.

Public exploit reaches PHP eval in vBulletin for unauthenticated code execution

Public exploit details released on July 27 show how an unauthenticated request can reach PHP's eval function inside vBulletin and run code on an unpatched forum server. The attack needs no account, administrative access, or interaction from another user, making any internet-facing vulnerable forum a direct target. SSD Secure Disclosure lists vBulletin 6.2.1 and earlier and 6.1.6 and earlier as affected, without giving a lower version boundary. Forum software is an attractive target because it is public by design, often runs with limited maintenance, and a single compromised server can host web shells, redirect visitors, or expose community member data. Administrators should confirm their version and patch level.

Check
Confirm the vBulletin version on any forum you run, apply the vendor's patches, and inspect the server for web shells and unexpected PHP files given that a public exploit exists.
Affected
Internet-facing vBulletin forums on 6.2.1 and earlier or 6.1.6 and earlier; an unauthenticated request reaches PHP eval for remote code execution, and working exploit details are now public.
Fix
Update vBulletin to a patched release, place a web application firewall in front of the forum, restrict server file writes, and monitor for unexpected processes spawned by the web server.

Confused deputy weaknesses still expose cross-tenant access in major clouds

Researchers showed that confused deputy weaknesses persist in Google Cloud and Microsoft Azure, where a trusted service can be tricked into acting on an attacker's behalf against resources it should not reach. The pattern shows up when one service holds broad permissions and accepts instructions or identifiers from a less-trusted source without verifying who is really asking, which can enable cross-tenant access or privilege escalation. It is the same class of issue behind recent findings in enterprise agent and integration tooling, where a component with a user's permissions follows attacker-supplied input. The takeaway is architectural: identity and authorization must be checked at every trust boundary, not assumed from the calling service.

Check
Review cloud integrations and automation where one service acts for another, and confirm each checks the real caller's identity and authorization rather than trusting the upstream service.
Affected
Organizations relying on cloud services and integrations that pass identifiers or instructions between trust boundaries; a broadly permissioned service can be steered into cross-tenant access or privilege escalation.
Fix
Scope service permissions tightly, validate the originating identity at every boundary, use per-tenant isolation and unique unguessable identifiers, and monitor for a trusted service accessing resources outside its expected scope.

DentaQuest notifies more than 23 million people after a data theft attack

Dental benefits administrator DentaQuest, part of Sun Life, is notifying more than 23 million people that their personal and health information was stolen in a May 2026 network intrusion. The company found unauthorized access on May 20 and determined attackers were in its network between May 17 and 20. Exposed data includes names, addresses, Social Security numbers, member, Medicaid, and Medicare identifiers, and dental and vision health details such as diagnoses, treatments, and billing. The extortion group ShinyHunters claimed responsibility and leaked roughly 234GB. DentaQuest has confirmed at least 15 million affected, with independent analysis putting the figure above 23 million, and is offering two years of monitoring.

Check
People with DentaQuest or associated Medicaid or Medicare dental coverage should watch for a notification, enroll in the offered monitoring, consider a credit freeze, and be alert to health-themed phishing.
Affected
More than 23 million DentaQuest members whose names, Social Security numbers, government program identifiers, and dental and vision health records were exposed and leaked, supporting identity theft and targeted fraud.
Fix
Affected people should freeze credit and monitor benefits statements. Organizations holding health data should segment it, enforce phishing-resistant MFA, monitor for bulk data access, and prepare for extortion-driven leaks.

Dysphoria botnet moves command and control onto the blockchain to resist takedown

An IoT botnet tracked as Dysphoria has adopted blockchain-based name services and relays built from its own victims after a March law enforcement operation disrupted related botnet infrastructure. Rather than hardcoding servers, it resolves command-and-control details through Ethereum and Solana naming systems, with addresses hidden inside fake IPv6 strings and recovered by a custom algorithm, which makes conventional server seizure harder. A separate relay build drops the attack modules and instead shuttles traffic between outside connections and remote servers through compromised devices. It spreads mainly through weak Telnet and SSH passwords and known device flaws. Researchers put its size above 200,000 bots, though that count is not independently verified.

Check
Take IoT and networking devices off direct internet exposure, replace default and weak Telnet and SSH credentials, patch known device flaws, and disable remote management where it is not needed.
Affected
Internet-exposed IoT and networking devices with weak Telnet or SSH passwords or unpatched flaws; these get recruited for denial-of-service attacks or as relays that hide the operator's real infrastructure.
Fix
Enforce strong unique device credentials, disable Telnet and unnecessary remote services, keep firmware patched or replace unsupportable devices, and monitor outbound connections for relay and blockchain name-service activity.

Cruciferra crypter uses vulnerable drivers and process ghosting to hide malware

Researchers detailed Cruciferra, a crypter service that packages Windows malware to evade detection using two notable techniques. It brings a vulnerable signed driver to disable security tooling, an approach known as bring-your-own-vulnerable-driver, and it uses process ghosting, where a malicious file is deleted before its code is mapped into a running process, so the running program has no backing file for tools to inspect. Together these let common payloads run while sidestepping many endpoint defenses. Crypter services matter because they lower the skill needed to deploy malware stealthily, letting many separate actors wrap their payloads in the same evasion layer rather than building it themselves.

Check
Enable vulnerable driver blocklisting on Windows, hunt for known bad drivers being loaded, and ensure endpoint tooling can detect process ghosting rather than relying on scanning files on disk.
Affected
Windows environments relying on file-based or easily disabled endpoint defenses; Cruciferra-wrapped malware disables protections through a vulnerable driver and runs with no backing file to scan.
Fix
Turn on Microsoft's vulnerable driver blocklist, restrict driver loading, deploy behavior-based detection that catches process ghosting and driver abuse, and alert on unexpected kernel driver installs.

Unpatched Fastjson flaw lets a single JSON request run code on Spring Boot apps

Security firms ThreatBook and Imperva report attackers targeting a critical flaw in Fastjson, Alibaba's widely used JSON library for Java. On affected Spring Boot applications, a malicious JSON request can execute code without authentication, running with the privileges of the Java process. Tracked as CVE-2026-16723 with an Alibaba-assigned score of 9.0, the confirmed chain needs Fastjson 1.2.68 through 1.2.83, a Spring Boot executable fat-JAR, a network-reachable path that feeds attacker-controlled JSON to the parser, and SafeMode left at its disabled default. Notably, the AutoType feature can stay off and no classpath gadget is required. As of July 25, Alibaba had not shipped a fixed 1.x version.

Check
Inventory Java services for Fastjson 1.x on the classpath, identify any endpoint that parses untrusted JSON, and enable SafeMode now rather than waiting for a fixed release.
Affected
Spring Boot applications packaged as fat-JARs using Fastjson 1.2.68 through 1.2.83 with SafeMode disabled (CVE-2026-16723); an unauthenticated JSON request reaches code execution, and no fixed 1.x version exists yet.
Fix
Enable SafeMode by setting fastjson.parser.safeMode to true, or switch to the noneautotype build, restrict network paths that parse untrusted JSON, and plan migration off Fastjson 1.x.