A malicious file identified by the SHA-256 hash f60c2c8b098025a65c50bc7eb3f2d92a5bd4a6f0915cbb921c0f275dbea410e1 was observed twice on October 29, 2026, by OffSeq Mirage honeypot sensors. The file is associated with attacker activity involving the T1105 technique (Ingress Tool Transfer) and is linked to attacker infrastructure located in the United States. This hash fingerprints a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to match this hash against files in their environments and security feeds to detect potential compromise.
CVE-2026-88967 is a server-side request forgery (SSRF) vulnerability in Grafana Enterprise affecting users with query access to Azure Monitor data sources. Exploitation allows an attacker to cause the server to send requests to attacker-controlled endpoints, potentially disclosing the Azure access token associated with the data source. This vulnerability affects multiple versions of Grafana Enterprise from 10.0.0 through 13.2.4. The issue has a high severity rating with a CVSS score of 7.7. A patch is available, and Grafana manages remediation for this cloud-hosted service.
A malicious file identified by the SHA-256 hash a863e21577e54cd763729803a621804da4b5030afa35bcf879ea3b3413488a66 was observed by OffSeq Mirage honeypot sensors during attacker activity on 2026-10-26. This file is associated with CVE-2026-109618 and linked to the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The file likely represents a malicious payload such as a dropper, web shell, miner, or post-exploitation tool used during the attack. The activity was traced back to attacker infrastructure in PS. Organizations are advised to match this hash against files in their environments and threat intelligence feeds.
A vulnerability in the TTLock Android application and associated smart-lock firmware prior to version 9.8.260718 involves a hardcoded static AES key. This flaw enables attackers within Bluetooth range to decrypt the per-pairing session key during BLE pairing, allowing them to forge authenticated requests to control the lock without user interaction.
This content announces the creation of an AI Security Wiki and an AI Secure by Design project, which provide a comprehensive, vendor-neutral resource for AI security governance, risk management, architecture, standards, and compliance. The authors emphasize that many recent AI-related security incidents stem from failures in fundamental security practices rather than AI technology itself. The projects aim to help organizations integrate security fundamentals into AI development and deployment to mitigate risks associated with AI-assisted attacks.
A malicious file identified by the SHA-256 hash 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08 was observed 9 times on 2026-10-24 by OffSeq Mirage honeypot sensors. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). This hash fingerprints a specific malicious payload which could be a dropper, web shell, miner, or post-exploitation tool. Organizations should match this hash against files in their environments and threat intelligence feeds to detect potential compromise.
A vulnerability exists where the system does not invalidate existing access tokens for sub-organization users during sensitive account management operations such as password resets, role changes, or sub-organization disablement. This allows previously issued tokens to remain active despite administrative changes to user access. Exploitation requires that these tokens be exposed to malicious actors. The vulnerability has a high severity rating with a CVSS score of 7.4.
This article discusses the security challenges posed by the adoption of agentic AI in software development. It highlights that rapid AI adoption without maturity and governance increases security risks, especially as AI agents become more autonomous. The piece outlines a three-phase, eight-stage AI Adoption Model that helps organizations understand their AI maturity and associated risks. It emphasizes the need for governance, developer upskilling, and observability to manage AI-driven security risks effectively. Most organizations are currently in early to mid-stages of AI adoption, making it critical to implement security controls and education programs now to prevent escalating risks as AI capabilities grow.
MISP versions prior to 2.5.48 contain an access control vulnerability in the proposal visibility logic. Users in a sharing group could view proposed changes to attributes or objects associated with that group regardless of the intended distribution level restrictions. Additionally, the owning organisation could not view proposals on its own organisation-only attributes. This flaw leads to unauthorized disclosure of proposed attribute changes.
Lychee is a free, open-source photo-management tool. Prior to 7.6.3, GET /api/v2/Zip authorizes album and photo archives through AlbumPolicy::canDownload() and PhotoPolicy::canDownload() without first enforcing AlbumPolicy::canAccess(). For a public, password-protected album with grants_download enabled, an unauthenticated attacker who knows the shared album identifier can download a ZIP archive without supplying the password or unlocking the album, even though browsing endpoints deny access. The archive exposes the album's photos and can include full-resolution originals and associated metadata when grants_full_photo_access is enabled. This issue is fixed in version 7.6.3.
The 'Iron Man System' is a commercial Phishing-as-a-Service (PhaaS) operation that provides criminal buyers with a self-hosted phishing kit. It includes over 2,360 phishing templates impersonating trusted entities such as postal services, banks, and government agencies, targeting 130 countries. The system features a bilingual Chinese-English interface, a subscription licensing model tied to vendor-controlled authorization servers, and a build registry with 911 published versions. Resecurity, in collaboration with Microsoft's Digital Crimes Unit and industry partners, mapped and disrupted this infrastructure. The kit was used to send approximately 1 billion phishing emails targeting 75,000 organizations, capturing around 17.4GB of telemetry data. Multiple domains associated with the infrastructure have been identified as indicators of compromise.
Traccar versions 5.7 through 6.16.0 have a cross-site request forgery (CSRF) vulnerability due to improper validation of the OAuth state parameter in the OpenID Connect callback. This flaw allows attackers to log victims into attacker-controlled accounts by tricking their browsers into loading a malicious authorization code. As a result, data entered by victims, such as registered devices, can be associated with the attacker's account.
A Canadian cybersecurity executive, Edward Dubrovsky, was arrested in Pennsylvania linked to alleged extortion activities associated with the FBI's crackdown on the ShinyHunters hacking group. The arrest is part of law enforcement efforts targeting this criminal hacking organization.
Hackers hijacked the .gh, .sl, and .as country-code top-level domains (ccTLDs), modifying authoritative DNS records and obtaining unauthorized HTTPS certificates for several Google domains and other organizations. Google blocked these unauthorized certificates in Chrome and worked with certificate authorities to revoke them. The incident highlights risks associated with third-party ccTLD management and certificate issuance. Google recommends domain owners monitor Certificate Transparency logs and implement restrictive CAA DNS records to prevent future unauthorized certificate issuance.
Hackers compromised third-party operators managing the authoritative DNS records for the country-code top-level domains (ccTLDs) of Ghana (.GH), American Samoa (.AS), and Sierra Leone (.SL). By modifying these DNS records, attackers were able to obtain unauthorized HTTPS certificates for several Google domains and other organizations' domains within these ccTLDs. This allowed them to hijack domains, redirect traffic to attacker-controlled infrastructure, and impersonate legitimate brands. Google confirmed its own systems were not compromised and worked with certificate authorities to revoke the fraudulent certificates and block them in Chrome. The incident highlights risks associated with third-party DNS registry security and certificate issuance processes.
CVE-2026-20362 is a Server-Side Request Forgery (SSRF) vulnerability in the web-based management interface of Cisco Finesse. It allows an unauthenticated remote attacker to send crafted HTTP requests that could lead to limited sensitive information disclosure from services associated with the affected device. The vulnerability arises from improper input validation of specific HTTP requests. It has a CVSS score of 7.2, indicating high severity. No patch or remediation information is currently provided.
A vulnerability was detected in linlinjava litemall up to 1.8.0. This affects an unknown part of the file litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAuthController.java of the component Login Endpoint. The manipulation results in improper restriction of excessive authentication attempts. The attack may be performed from remote. A high complexity level is associated with this attack. It is indicated that the exploitability is difficult. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
YesWiki versions prior to 4.6.7 have a cross-site request forgery (CSRF) vulnerability in the ajaxdeletepage handler. This flaw allows an attacker to trick a logged-in administrator or page owner into sending a crafted GET request with a jsonp_callback parameter, which deletes arbitrary pages permanently without verifying a CSRF token. The deletion affects pages along with their associated access control lists, links, triples, comments, and referrers.
Missing cryptographic step in the DSTU 7624 CCM mode implementation (KCcmBlockCipher) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can observe encrypted messages of known or chosen content to forge ciphertexts with valid authentication tags, via messages encrypted without associated data. The cause is that the G1 block, which binds the nonce, the message length and the parameter flags into the CBC-MAC, was processed only when associated data was present. Without associated data the tag was a CBC-MAC of the plaintext alone, independent of the nonce. Only applications that use KCcmBlockCipher directly and supply no associated data are affected.