Interfaz en español. Las fichas, los resúmenes y las fuentes conservan su idioma original.
Cold chain attacks, compromised updates and credential recovery
Refrigeration incidents continued in Europe, malicious software reached trusted distribution channels, and several providers required customers to replace exposed credentials. This edition covers changes since the October 30 cutoff, including the weekend, and separates released fixes from work still required to recover.
Refrigeration controls and exposed Node-RED interfaces
Qué cambió
EU authorities confirmed another wave of refrigeration incidents on November 1–2. US agencies describe targeting of controllers and cold chain monitoring, where changed settings can damage inventory or remove temperature visibility. Separately, VulnCheck observed malicious Node-RED flow deployments against canaries; those observations do not establish compromised industrial sites.
Qué revisar
Remove public access to refrigeration administration, secure necessary maintenance access and verify actual temperatures, setpoints and alarm delivery with operations. For the affected SIMATIC IoT2050 models running Industrial OS with Node-RED, install V4.3.4-1 or later, enforce authentication and inspect deployed flows.
Avisos relacionados 2
- Actuar ahoraNuevo en RadarCold chain attacks: protect refrigeration controls and monitoring
- Actuar ahoraNuevo en RadarNode-RED: exploitation attempts observed against unauthenticated interfaces
Compromised updates leave credentials and persistence behind
Qué cambió
OpsShield reports that a malicious cPGuard update accessed root credentials and other secrets; its later disclosure supersedes parts of the initial notice. Cursor identified malicious Claude Code extension versions 2.1.312 and 2.1.313 with SSH persistence. LiteLLM’s October 30 clarification identifies its replacement image signing key: signatures made with the previous key do not establish that an artifact is clean.
Qué revisar
For cPGuard, follow the 5.88.26 cleanup guidance, replace exposed credentials and revoke trust in compromised SSH keys on other hosts. For Cursor, correlate extension installation with endpoint execution and remove persistence. For LiteLLM, compare artifact digests and key provenance, rebuild affected environments and rotate reachable secrets.
Avisos relacionados 3
- Actuar ahoraNuevo en RadarcPGuard: malicious updates expose server credentials
- Actuar ahoraNuevo en RadarCursor: malicious Claude Code extensions attempt persistent SSH access
- Actuar ahoraSeguimientoLiteLLM 1.107.0: check where it ran
Northflank and Chainalysis: containment does not complete customer recovery
Qué cambió
Northflank’s November 6 update places the earliest known secret decryption at 02:39–03:08 UTC on October 30 and keeps its rotation requirement. Chainalysis began a phased restoration of KYT and Address Screening on November 6; that is not full restoration of every product. Its recovery process requires password resets and API key rotation where applicable.
Qué revisar
Rotate Northflank project and integration secrets at their issuers, revoke old credentials and review usage and billing. Chainalysis customers should coordinate trusted IP access through their established account contact, then reset credentials before resuming transactions. Follow the current provider notice for access to other products.
Avisos relacionados 2
- Actuar ahoraNuevo en RadarNorthflank: rotate project and integration secrets after incident
- Actuar ahoraNuevo en RadarChainalysis confirms credential exposure and suspends KYT
Wallet recovery requires more than restoring service
Qué cambió
Binance’s November 3 preliminary findings connect a fake recruitment assignment and internal AI tooling to access to wallet signing. Its reported 98% replenishment is not recovery of 98% of stolen assets. Separately, BTCPay reports theft affecting servers on 2.4.1 or earlier; its recovery scope also includes servers updated only after the November 1 warning.
Qué revisar
Review access from employee tooling to deployment tokens and signing services, including persistent delegations. For BTCPay servers within the stated scope, preserve evidence, rebuild on a fresh VM with a new wallet and seed, and rotate exposed host secrets. Updating the old host or restoring its full image is insufficient.
Avisos relacionados 2
- Revisar esta semanaSeguimientoBinance links wallet breach to a fake job interview and internal AI tooling
- Actuar ahoraNuevo en RadarBTCPay Server: affected hosts need a fresh VM and wallet
Linux: verify the running kernel and the replacement fleet
Qué cambió
AWS describes demonstrated unauthenticated code execution through CVE-2026-98432 on hosts with an MPTCP listener, while reporting no evidence of attacks. Amazon Linux fixes and GameLift Servers images are available. RDS/Aurora OS patch availability remains a November 6 target in the reviewed bulletin, not a verified completed rollout.
Qué revisar
Apply the distributor correction and activate the fixed kernel. Replace affected GameLift container fleets created before November 2 at 21:06 UTC and managed EC2 fleets created before November 3 at 01:55 UTC; move session traffic before retiring old fleets. Check the current RDS/Aurora patch state and keep database ports off the public internet.
Avisos relacionados 1
- Revisar esta semanaNuevo en RadarLinux IPv4/TCP: check exposed kernels for CVE-2026-98432
Brotli and certificate updates need checks by service
Qué cambió
AWS now reports corrected CodeBuild curated images and Lambda Node.js runtimes; pinned or custom images still need customer action. Solace reports completed Cloud Console and Micro-Integrations fixes and Schema Registry 1.1.3, while its unused Event Broker appliance RPM remains scheduled for replacement. These product states must not be collapsed into one universal completion claim.
Qué revisar
Rebuild affected containers, update image pins and verify Lambda runtime patch identifiers. Apply Schema Registry 1.1.3 where needed. Separately, finish replacing affected eMudhra certificate chains and application trust stores; an elapsed provider rollout date does not prove that customer certificates or deployed bundles were replaced.
Avisos relacionados 2
- Actuar ahoraSeguimientoBrotli: patch runtimes and proxies that decode untrusted data
- Actuar ahoraSeguimientoeMudhra: replace affected certificates and review application trust
Application fixes can leave a second task
Qué cambió
Rails Active Storage is exposed when untrusted uploads reach ImageMagick under a permissive coder policy; Disk storage can also expose files readable by the application. In n8n, saved workflows with deprecated code nodes can continue to execute after an upgrade. GitLab installations using their own Ruby runtime do not receive the runtime correction by updating GitLab alone.
Qué revisar
Upgrade Active Storage to 8.0.5.2 or 8.1.4.1 and verify the effective ImageMagick policy; investigate and replace exposed application secrets. Upgrade n8n and migrate Function, Function Item and LangChain Code nodes. For GitLab with a separate Ruby runtime, apply Ruby 3.3.13, 3.4.12, 4.0.9 or a later corrected release.
Avisos relacionados 3
- Actuar ahoraNuevo en RadarRails Active Storage: uploaded images can expose application secrets
- Revisar esta semanaNuevo en Radarn8n: update and migrate workflows using deprecated code nodes
- Revisar esta semanaSeguimientoGitLab issues an emergency code execution fix
WordPress and Drupal exploitation; CWP2Shell demonstration
Qué cambió
BeyondTrust now lists Remote Support 26.3.1 as fixed alongside the BT26-05-RS patch. CISA added the WordPress core upgrade flaw CVE-2026-119977 to KEV on November 3. Drupal confirms active exploitation of Commerce Core CVE-2026-118539. By contrast, CWP2Shell is a demonstrated chain to root, with a valid hosting username required at its unauthenticated entry; the reviewed research does not establish actual attacks for these CVEs.
Qué revisar
For BeyondTrust, verify BT26-05-RS or Remote Support 26.3.1 or later; older releases must upgrade before they can accept the patch. Install WordPress 7.1.4 or the corrected release for the deployed branch and review prior upgrade activity. Update Commerce Core to 3.3.13 or 8.x-2.41 and audit orders. For Control Web Panel, install the vendor’s recommended 1.30.1 security update and restrict access to administration.
Avisos relacionados 4
- Actuar ahoraSeguimientoBeyondTrust Remote Support: exploited appliance flaw
- Actuar ahoraNuevo en RadarWordPress: patch the exploited core upgrade flaw
- Actuar ahoraNuevo en RadarDrupal Commerce: patch active exploitation and audit orders
- Actuar ahoraNuevo en RadarCWP2Shell: update Control Web Panel and restrict panel access
Browser fixes are available; the next Node.js release is still planned
Qué cambió
Chrome 157 includes seven Critical fixes in its November 3 desktop release. Mozilla fixed CVE-2026-120572 in Firefox 159.0.1. Neither reviewed announcement reports active exploitation. Node.js separately plans security releases for 22.x, 24.x and 26.x on November 11 or shortly after, with High as the maximum announced severity.
Qué revisar
Update and relaunch managed browsers, then verify their running versions. Inventory Node.js deployments and prepare compatibility tests and a rollout window. The November Node.js fixes and CVE details are not yet published; preparation does not replace the existing Brotli updates.
Avisos relacionados 3
- Actuar ahoraNuevo en RadarChrome 157: update and relaunch after seven critical fixes
- Revisar esta semanaNuevo en RadarFirefox: update to 159.0.1 and relaunch the browser
- Revisar esta semanaNuevo en RadarNode.js: prepare for security releases planned for November 11
Mobile exploits and fake verification prompts expose account access
Qué cambió
Sekoia recovered three Poisoned Source exploit chains for specific iOS and Android/Chrome versions. The analyzed chains use already patched vulnerabilities and do not work against fully updated devices; attribution to APT29 is Sekoia’s assessment with moderate to high confidence. COLCERT’s Amatera warning describes Windows credential and cookie theft through fake verification prompts and impersonated software pages.
Qué revisar
Check operating system, browser and device security updates. Teach staff to report verification pages that request command execution. Where evidence suggests compromise, preserve relevant records, contain the device and revoke affected sessions and exposed credentials from a trusted system. Installing updates or cleaning the device does not invalidate stolen sessions.
Avisos relacionados 2
- Revisar esta semanaNuevo en RadarPoisoned Source: mobile exploits target cookies and private data
- Revisar esta semanaNuevo en RadarAmatera in LATAM: fake verification prompts put business access at risk
CyberStrikeAI used familiar paths to domain compromise
Qué cambió
Kaspersky reports activity against educational organizations in Latin America and Africa. In the detailed incident, attackers already controlled a SQL Server before deploying CyberStrikeAI. An LLM on the control server selected actions; the implant executed conventional commands, including credential theft and movement through SMB and WMI. This does not establish a new vulnerability in every SQL Server.
Qué revisar
Review unexpected child processes of sqlservr.exe, scheduled tasks, credential access and privileged account use. Limit server to server administration paths and investigate suspicious SMB/WMI activity. Correlate the published indicators with local evidence rather than treating use of an AI tool as proof of attribution.
Avisos relacionados 1
- Revisar esta semanaNuevo en RadarCyberStrikeAI: attackers compromised domain admins in 3–4 days
Amadeus: reservation data exposed through airline bookings
Qué cambió
Amadeus and airline notices confirm unauthorized access to reservation data. Names, booking references and itineraries appear in the notices; additional fields vary by airline and customer subset. Counts mix passengers and bookings, so they cannot be added into a unique victim total. Amadeus says it found no evidence of access to payment or financial data.
Qué revisar
Travel teams should check the relevant carrier notice, verify unexpected itinerary or payment messages through established channels and follow instructions for affected booking references. Keep the provider’s statements separate from an independent forensic conclusion.
Avisos relacionados 1
- Revisar esta semanaNuevo en RadarAmadeus booking data breach: airlines notify affected passengers
Avisos al corte
- Actuar ahoraNuevo en RadarCold chain attacks: protect refrigeration controls and monitoring
- Actuar ahoraNuevo en RadarNode-RED: exploitation attempts observed against unauthenticated interfaces
- Actuar ahoraNuevo en RadarcPGuard: malicious updates expose server credentials
- Actuar ahoraNuevo en RadarCursor: malicious Claude Code extensions attempt persistent SSH access
- Actuar ahoraSeguimientoLiteLLM 1.107.0: check where it ran
- Actuar ahoraNuevo en RadarNorthflank: rotate project and integration secrets after incident
- Actuar ahoraNuevo en RadarChainalysis confirms credential exposure and suspends KYT
- Revisar esta semanaSeguimientoBinance links wallet breach to a fake job interview and internal AI tooling
- Actuar ahoraNuevo en RadarBTCPay Server: affected hosts need a fresh VM and wallet
- Revisar esta semanaNuevo en RadarLinux IPv4/TCP: check exposed kernels for CVE-2026-98432
- Actuar ahoraSeguimientoBrotli: patch runtimes and proxies that decode untrusted data
- Actuar ahoraSeguimientoeMudhra: replace affected certificates and review application trust
- Actuar ahoraNuevo en RadarRails Active Storage: uploaded images can expose application secrets
- Revisar esta semanaNuevo en Radarn8n: update and migrate workflows using deprecated code nodes
- Revisar esta semanaSeguimientoGitLab issues an emergency code execution fix
- Actuar ahoraSeguimientoBeyondTrust Remote Support: exploited appliance flaw
- Actuar ahoraNuevo en RadarWordPress: patch the exploited core upgrade flaw
- Actuar ahoraNuevo en RadarDrupal Commerce: patch active exploitation and audit orders
- Actuar ahoraNuevo en RadarCWP2Shell: update Control Web Panel and restrict panel access
- Actuar ahoraNuevo en RadarChrome 157: update and relaunch after seven critical fixes
- Revisar esta semanaNuevo en RadarFirefox: update to 159.0.1 and relaunch the browser
- Revisar esta semanaNuevo en RadarNode.js: prepare for security releases planned for November 11
- Revisar esta semanaNuevo en RadarPoisoned Source: mobile exploits target cookies and private data
- Revisar esta semanaNuevo en RadarAmatera in LATAM: fake verification prompts put business access at risk
- Revisar esta semanaNuevo en RadarCyberStrikeAI: attackers compromised domain admins in 3–4 days
- Revisar esta semanaNuevo en RadarAmadeus booking data breach: airlines notify affected passengers
Los recuentos describen los avisos seleccionados para esta edición, no incidentes detectados por Oktsec. Los grupos se superponen. Los enlaces abren las versiones actuales de los avisos.
Controles recomendados
- 01
Identify exposed administration and validate operational safety with the people running refrigeration and other connected equipment.
- 02
Confirm the corrected kernel, runtime, firmware or image is actually running; retain proof for each deployment.
- 03
Complete the second task after patching: rotate exposed credentials, revoke sessions and SSH trust, migrate saved workflows or rebuild affected hosts.
- 04
Keep exploit demonstrations, observed attacks, provider statements and scheduled releases separate in the response record.
Fuentes de este resumen 127 referencias
Fuentes
Los datos técnicos provienen de estas fuentes. Las prioridades y las acciones recomendadas son el análisis de Oktsec.
- EU joint statement: recurring refrigeration incidents, November 4European Commission / ENISA / Europol / CSIRTs Network / EU-CyCLONe · Aviso gubernamental · Revisado 5 nov 2026 UTC
- CSIRTs Network: collection of national refrigeration advisoriesENISA / CSIRTs Network · Aviso gubernamental · Revisado 5 nov 2026 UTC
- Siemens SSA-834709: affected product and correctionSiemens · Aviso del proveedor · Revisado 5 nov 2026 UTC
- Chainalysis incident updates through November 4Chainalysis · Aviso del proveedor · Revisado 5 nov 2026 UTC
- AWS 2026-160: kernel, node and managed-service responseAWS · Aviso del proveedor · Revisado 5 nov 2026 UTC
- AWS trust bundle updates: ALB certificates and Lambda deployment actionsAWS · Aviso del proveedor · Revisado 5 nov 2026 UTC
- GitLab critical patch releaseGitLab · Aviso del proveedor · Revisado 5 nov 2026 UTC
- BT26-05 security advisoryBeyondTrust · Aviso del proveedor · Revisado 5 nov 2026 UTC
- ARMORY CASTLE investigation and responseBeyondTrust · Aviso del proveedor · Revisado 5 nov 2026 UTC
- US joint fact sheet: hardening refrigeration and cold chain monitoring, November 5CISA / FBI / HHS / USDA / DoT · Aviso gubernamental · Revisado 5 nov 2026 UTC
- CERT-FR refrigeration-controller alert; guidance revised October 16CERT-FR / ANSSI · Aviso gubernamental · Revisado 5 nov 2026 UTC
- Copeland/Dixell XWEB security and recovery bulletin, October 14Copeland Controls / Dixell France · Aviso del proveedor · Revisado 5 nov 2026 UTC
- Poisoned Source: mobile delivery, recovered chains and attribution assessmentSekoia · Informe de investigación · Revisado 5 nov 2026 UTC
- Latest incident disclosure and recovery guidanceOPSSHIELD · Aviso del proveedor · Revisado 5 nov 2026 UTC
- Earlier advisory: affected updates and log limitationsOPSSHIELD · Aviso del proveedor · Revisado 5 nov 2026 UTC
- CISA KEV: CVE-2024-27834 added November 4; other chain CVEs have earlier entriesCISA · Aviso gubernamental · Revisado 5 nov 2026 UTC
- GHSA-f3w6-w445-fwh9: scope and credential recoveryRuby on Rails · Aviso del proveedor · Revisado 5 nov 2026 UTC
- Rails 8.1.4.1: ImageMagick policy and compatibility changesRuby on Rails · Aviso del proveedor · Revisado 5 nov 2026 UTC
- Rails 8.0.5.2: corrected branch releaseRuby on Rails · Aviso del proveedor · Revisado 5 nov 2026 UTC
- November 2026 security release announcementNode.js · Aviso del proveedor · Revisado 5 nov 2026 UTC
- Mozilla MFSA 2026-123: Firefox 159.0.1Mozilla · Aviso del proveedor · Revisado 4 nov 2026 UTC
- COLCERT AL 20261103 125: regional warning and response guidanceCOLCERT · Aviso gubernamental · Revisado 4 nov 2026 UTC
- Amatera detections in Latin America during the first half of 2026ESET · Informe de investigación · Revisado 4 nov 2026 UTC
- ACR Stealer: two intrusion chains observed from April to JuneMicrosoft Security Research · Informe de investigación · Revisado 4 nov 2026 UTC
- May research into impersonated AI and development tool pagesStraiker · Informe de investigación · Revisado 4 nov 2026 UTC
- Amadeus statement on the booking display vulnerabilityAmadeus · Aviso del proveedor · Revisado 4 nov 2026 UTC
- JAL and Japan Transocean Air: customer scope and responseJapan Airlines · Aviso del proveedor · Revisado 4 nov 2026 UTC
- ANA: unauthorized access to passenger reservation dataANA · Aviso del proveedor · Revisado 4 nov 2026 UTC
- Cathay Pacific: reservation data incident at AmadeusCathay Pacific · Aviso del proveedor · Revisado 4 nov 2026 UTC
- CNA reports Singapore Airlines’ November 3 statementCNA · Informe de prensa · Revisado 4 nov 2026 UTC
- EFE: Asian airlines affected by the Amadeus data breachEFE · Informe de prensa · Revisado 4 nov 2026 UTC
- Apple security releases and device eligibilityApple · Aviso del proveedor · Revisado 4 nov 2026 UTC
- DarkSword: earlier research and patch context, separate from Poisoned SourceGoogle Threat Intelligence Group · Informe de investigación · Revisado 4 nov 2026 UTC
- Chrome for Android: March 12 security updateGoogle · Aviso del proveedor · Revisado 4 nov 2026 UTC
- CVE-2026-3910: corresponding Chrome security fixGoogle · Aviso del proveedor · Revisado 4 nov 2026 UTC
- CVE-2025-27038: Qualcomm CNA record for Adreno GPU driversQualcomm, via CVE Program · Aviso del proveedor · Revisado 4 nov 2026 UTC
- Red Hat: affected products and mitigation limitsRed Hat · Aviso del proveedor · Revisado 4 nov 2026 UTC
- Red Hat: affected branches and issued security errataRed Hat · Aviso del proveedor · Revisado 4 nov 2026 UTC
- AWS: Brotli runtime verification and CodeBuild correctionsAWS · Aviso del proveedor · Revisado 4 nov 2026 UTC
- Solace: corrected components and Schema Registry 1.1.3Solace · Aviso del proveedor · Revisado 4 nov 2026 UTC
- CyberStrikeAI: investigation of attacks on educationKaspersky Securelist · Informe de investigación · Revisado 4 nov 2026 UTC
- Education campaign: observed dates and incident timelineKaspersky · Informe de investigación · Revisado 4 nov 2026 UTC
- Earlier CyberStrikeAI infrastructure and FortiGate targeting — separate activityTeam Cymru · Informe de investigación · Revisado 4 nov 2026 UTC
- CWP2Shell: research demonstration and staged fixesVulnCheck · Informe de investigación · Revisado 4 nov 2026 UTC
- Control Web Panel: security release 1.30.1Control Web Panel · Aviso del proveedor · Revisado 4 nov 2026 UTC
- CVE-2026-73695: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-73696: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-73697: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-77876: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-77877: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-77878: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-77879: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-77880: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-77881: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- CVE-2026-104080: CNA affected rangeVulnCheck CNA · Informe de investigación · Revisado 4 nov 2026 UTC
- Chrome 157: desktop stable security releaseGoogle · Aviso del proveedor · Revisado 4 nov 2026 UTC
- WordPress 7.1.4 security releaseWordPress · Aviso del proveedor · Revisado 3 nov 2026 UTC
- Wordfence: affected branches and corrected releasesWordfence · Informe de investigación · Revisado 3 nov 2026 UTC
- Wordfence CNA: CVE-2026-119977 branch rangesWordfence / CVE Program · Informe de investigación · Revisado 3 nov 2026 UTC
- Node-RED exploitation attempts in canary telemetryVulnCheck · Informe de investigación · Revisado 3 nov 2026 UTC
- Secure the Node-RED editor and admin APINode-RED · Aviso del proveedor · Revisado 3 nov 2026 UTC
- Northflank incident updates and rotation guidanceNorthflank · Aviso del proveedor · Revisado 3 nov 2026 UTC
- BTCPay incident scope and recovery guidanceBTCPay Server · Aviso del proveedor · Revisado 3 nov 2026 UTC
- n8n: deprecated code nodes and migration requirementsn8n · Aviso del proveedor · Revisado 3 nov 2026 UTC
- CNA record: CVE mapping and affected branchesVulnCheck · Informe de investigación · Revisado 3 nov 2026 UTC
- Binance November 3 preliminary findings: fake interview, internal AI tooling and signing accessBinance News · official account · Aviso del proveedor · Revisado 3 nov 2026 UTC
- Binance November 3 report: containment, replenishment and investigation statusBinance News · official account · Aviso del proveedor · Revisado 3 nov 2026 UTC
- ONYPHE: Danfoss StoreView exposure, October 13; updated October 15ONYPHE · Informe de investigación · Revisado 2 nov 2026 UTC
- ONYPHE: Copeland/Dixell exposure study, October 22ONYPHE · Informe de investigación · Revisado 2 nov 2026 UTC
- EL PAÍS: further European supermarket refrigeration incidents, November 2EL PAÍS · Informe de prensa · Revisado 2 nov 2026 UTC
- Linux CNA: IPv4/TCP mechanism and upstream branch fixesLinux · Aviso del proveedor · Revisado 1 nov 2026 UTC
- Amazon Linux: affected packages and CVSS assessmentAmazon Linux · Aviso del proveedor · Revisado 1 nov 2026 UTC
- Binance recovery update #4: 95% replenishment and phased withdrawalsBinance · Aviso del proveedor · Revisado 1 nov 2026 UTC
- Binance Chinese official account: first-phase BTC withdrawals have begunBinance Chinese · Aviso del proveedor · Revisado 1 nov 2026 UTC
- FBI October 31 attribution: North Korean TraderTraitor activityFBI · Aviso gubernamental · Revisado 1 nov 2026 UTC
- SA-CONTRIB-2026-254: Commerce Core access bypassDrupal · Aviso del proveedor · Revisado 1 nov 2026 UTC
- Commerce Core 3.3.13 security releaseDrupal · Aviso del proveedor · Revisado 1 nov 2026 UTC
- Commerce Core 8.x-2.41 security releaseDrupal · Aviso del proveedor · Revisado 31 oct 2026 UTC
- Cursor security notice: malicious Anthropic.claude-code versionsCursor · Aviso del proveedor · Revisado 31 oct 2026 UTC
- Microsoft analysis: persistent SSH backdoor in the Cursor extensionMicrosoft Security Research · Informe de investigación · Revisado 31 oct 2026 UTC
- Binance recovery update #3: 90% replenishment and reserve-proof timelineBinance · Aviso del proveedor · Revisado 31 oct 2026 UTC
- October 21 supply chain incidentLiteLLM · Aviso del proveedor · Revisado 31 oct 2026 UTC
- Binance security incident update #2: additional breach points and replacement assetsBinance · Aviso del proveedor · Revisado 31 oct 2026 UTC
- PAN-OS October 29 matrix and Transporter correctionPalo Alto Networks · Aviso del proveedor · Revisado 31 oct 2026 UTC
- Microsoft guidance: PHP2Shell, Brotli and eMudhraMicrosoft · Aviso del proveedor · Revisado 31 oct 2026 UTC
- CloudLinux OS: separate system, EasyApache and alt-php Brotli fixesCloudLinux · Aviso del proveedor · Revisado 30 oct 2026 UTC
- Binance October 30 statement: estimated impact, initial investigation and responseBinance · Aviso del proveedor · Revisado 30 oct 2026 UTC
- BWEnews tally reported by BBX: $5.643 billion in outflows at 21:22 UTCBBX / BWEnews · Informe de prensa · Revisado 30 oct 2026 UTC
- Binance 14: second transfer at 21:44:11 UTCEtherscan · Informe de investigación · Revisado 30 oct 2026 UTC
- Binance: investigation into a potential security issueBinance · Aviso del proveedor · Revisado 30 oct 2026 UTC
- Binance: $2.54 billion frozen, not a final loss estimateBinance · Aviso del proveedor · Revisado 30 oct 2026 UTC
- Binance 14: EIP-7702 delegation at 20:20:59 UTCEtherscan · Informe de investigación · Revisado 30 oct 2026 UTC
- Binance 14: ETH and token transfers at 20:24:23 UTCEtherscan · Informe de investigación · Revisado 30 oct 2026 UTC
- Binance Hot Wallet 34: 780 million USDC transferEtherscan · Informe de investigación · Revisado 30 oct 2026 UTC
- EIP-7702 delegation and transfer analysisOdysseas / Phylax · Informe de investigación · Revisado 30 oct 2026 UTC
- Circle: more than 800 million USDC frozenJeremy Allaire / Circle · Aviso del proveedor · Revisado 30 oct 2026 UTC
- Tether: more than 1.567 billion USDT frozenPaolo Ardoino / Tether · Aviso del proveedor · Revisado 30 oct 2026 UTC
- EIP-7702: account code delegation and security considerationsEthereum Improvement Proposals · Informe de investigación · Revisado 30 oct 2026 UTC
- MongoDB CNA record: Compass CVE-2026-115929MongoDB · Aviso del proveedor · Revisado 28 oct 2026 UTC
- PAN-OS 12.2.4-h1 addressed issuesPalo Alto Networks · Aviso del proveedor · Revisado 27 oct 2026 UTC
- PAN-OS 12.1.7-h11 addressed issuesPalo Alto Networks · Aviso del proveedor · Revisado 27 oct 2026 UTC
- Java follow-up alert: root certificate removalOracle · Aviso del proveedor · Revisado 27 oct 2026 UTC
- Runtime checks and mitigations for eMudhra certificatesOracle · Aviso del proveedor · Revisado 27 oct 2026 UTC
- Updated PHP Windows builds for Brotli security fixPHP · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Chrome and Android response to compromised eMudhra intermediatesGoogle · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Python 3.15.2 security releasePython · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Python 3.14.10 security releasePython · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Python 3.13.18 security releasePython · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Python 3.12.16 security releasePython · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Python 3.11.18 security releasePython · Aviso del proveedor · Revisado 26 oct 2026 UTC
- Application updates for compromised eMudhra certificatesGoogle · Aviso del proveedor · Revisado 26 oct 2026 UTC
- IO::Compress::Brotli 0.023 security releaseIO::Compress::Brotli maintainers · Aviso del proveedor · Revisado 25 oct 2026 UTC
- Java security alert CVE-2026-91403Oracle · Aviso del proveedor · Revisado 25 oct 2026 UTC
- Python ssl certificate denylist announcementPython · Aviso del proveedor · Revisado 25 oct 2026 UTC
- CPython certificate denylist merged changePython · Aviso del proveedor · Revisado 25 oct 2026 UTC
- MongoDB Compass 1.53.1 releaseMongoDB · Aviso del proveedor · Revisado 25 oct 2026 UTC
- Electron 44.9.1 certificate mitigationElectron · Aviso del proveedor · Revisado 25 oct 2026 UTC
- Definitive investigation: the attack chain behind release 1.107.0LiteLLM · Aviso del proveedor · Revisado 24 oct 2026 UTC
- October Node.js security releasesNode.js · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Brotli exposure, fixed releases and mitigationsOpenAI · Patch the Planet · Informe de investigación · Revisado 24 oct 2026 UTC
- Brotli 1.2.1 security releaseGoogle Brotli · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Brotli 1.1.1 security releaseGoogle Brotli · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Brotli 1.0.10 security releaseGoogle Brotli · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Bun 1.4.4 Brotli dependencyBun · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Envoy Brotli decompressor advisoryEnvoy · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Istio security advisory and fixed releasesIstio · Aviso del proveedor · Revisado 24 oct 2026 UTC
- Node2Shell research demonstrationImperva · Informe de investigación · Revisado 23 oct 2026 UTC
Identificá qué requiere atención.
Alertas prioritarias y resúmenes de seguridad. Evidencia, sistemas afectados y próximos pasos.
Comprobando disponibilidad…