Search/bitbucket
Vendor

bitbucket

Known CVEs
0
Highest CVSS
In KEV
0
Vendor
xnbd
Connections
17 relationships
Trivy, Not LiteLLM Behind the 2,500 Org Compromise
Most of the 2,500 organizations believed to have been affected by the LiteLLM supply chain attack were actually exposed before, SOCRadar reports. The compromise was blamed on and claimed by TeamPCP, the threat actor behind multiple open source software (OSS) supply chain attacks involving the Shai-Hulud worm. It started with Aqua Security’s Trivy scanner and propagated downstream to multiple packages and repositories in a ripple effect fueled by the malware’s worm-like behavior and by the automated inclusion of the malicious libraries in more builds. More than 2,500 organizations were likely affected by the LiteLLM attack, CloudSEK and HudsonRock said earlier this week. According to SOCRadar, most of them were victims of the Trivy compromise, not LiteLLM. All the compromises associated with TeamPCP followed a similar pattern: malicious code was automatically executed when the infected package was fetched and run to harvest credentials, tokens, API keys, and other secrets. Additionally, the worm used stolen developer secrets to modify accessible packages and push the malicious versions to the registry, expanding the attack surface. This is how LiteLLM was compromised and how two poisoned package versions were published on March 24 and stayed online for roughly 40 minutes. They were injected with a .pth file that Python automatically executed at interpreter startup, even if LiteLLM was never imported, bypassing ignore-scripts protections. The compromise timeframe According to SOCRadar, a close examination of the LiteLLM incident data revealed per-organization records for 2,188 entities, including timestamps, credential types, CI/CD platforms, and domains. “Every record carries first-seen and last-seen timestamps. The earliest is March 19 at 18:05 UTC and the latest is March 24 at 20:09 UTC, a span of just over five days,” the cybersecurity firm notes. For 2,085 organizations, or 95% of the 2,188 that were identified, data collection activity ended before March 24, when the poisoned LiteLLM packages were published to the registry. “That timing lines up with the upstream Trivy compromise rather than the LiteLLM install window. The 40 minutes everyone reported was the closing act, not the whole play,” SOCRadar says. The earliest collection occurred 18 minutes after the malicious Trivy build was published on March 19. The activity surged on March 22 and March 23 when malicious Trivy images were live on Docker Hub, and closed on March 24 after PyPI quarantined the packages. “[This] is what persistence on already-infected hosts looks like: the .pth payload kept running after the source of the infection was gone,” SOCRadar notes. The compromise involved six CI/CD platforms, namely GitHub Actions, GitLab CI, Jenkins, Bitbucket, CircleCI, and Buildkite, and impacted organizations worldwide, with Germany, Brazil, and France affected the most. Stolen, now brokered secrets The malware targeted secrets broadly, but over 1,000 organizations exposed JWT and auth tokens. Hundreds of them exposed private keys, AWS access keys, GitLab tokens, OpenAI API keys, Slack webhooks, GitHub Actions tokens, and Google API keys. “The highest secret count in the set is roughly 3,477 [the organization has not been named], followed by roughly 3,459. Several high-secret rows rest on very few files or repositories. One row carries 3,459 secrets across just six files,” SOCRadar notes. The cybersecurity firm also points out that committer email addresses were compromised across over 1,100 organizations. In those cases, the attackers have both developer identities and machine tokens. “Of the 2,188 organizations in the record-level set, 56% are rated high confidence, 39% medium, and 6% low, with figures rounded. Headline reporting cites 2,500+ organizations; the difference reflects which records carry attributable identifiers,” SOCRadar notes. “High-confidence matches are keyed on CI host identity and legitimate committer domains, meaning whose systems a captured file came from, rather than any observed use of a stolen credential. These are exposure figures rather than confirmed compromises, drawn from a reconstructed sample rather than a complete census,” it continues. The stolen information is already being brokered. One threat actor is offering on Telegram a collection of LiteLLM, Trivy, and CanisterWorm data, likely compiled at various stages of the campaign. Related: Over 400 NPM Packages Infected in ChainDrop Supply Chain Attack Related: North Korean Hackers Target Open Source Developers in Supply Chain Attacks Related: North Korean Hackers Blamed for Mastra NPM Supply Chain Attack Related: Hackers Exploiting Unpatched GeoServer Zero-Day
securityweek.comAug 14, 2026extracted
Risolte vulnerabilità in prodotti Atlassian
Risolte vulnerabilità in prodotti Atlassian Alert AL07/260618/CSIRT-ITA Sintesi Rilasciati aggiornamenti di sicurezza per risolvere alcune vulnerabilità di cui 8 con gravità “critica” e 24 con gravità “alta” presenti nei prodotti Bamboo, Jira, Bitbucket, Confluence e Crowd, nelle versioni Data Center e Server di Atlassian. Tipologia Security Restrictions Bypass Data Manipulation Authentication Bypass Denial of Service Information Disclosure Remote Code Execution Prodotti e/o versioni affette Bamboo Data Center e Server 12.1.x, versione 12.1.7 (LTS) e precedenti 12.0.x, versione 12.0.2 e precedenti 11.0.x, versione 11.0.8 e precedenti 10.2.x, versione 10.2.19 (LTS) e precedenti 10.1.x, versione 10.1.1 e precedenti 10.0.x, versione 10.0.3 e precedenti Bitbucket Data Center e Server 10.3.x, versione 10.3.0 10.2.x, versione 10.2.3 (LTS) e precedenti 10.1.x, versione 10.1.5 e precedenti 10.0.x, versione 10.0.2 e precedenti 9.6.x, versione 9.6.5 e precedenti 9.5.x, versione 9.5.2 e precedenti 9.4.x, versione 9.4.20 (LTS) e precedenti 9.3.x, versione 9.3.2 e precedenti 9.2.x, versione 9.2.1 e precedenti 9.1.x, versione 9.1.1 e precedenti 9.0.x, versione 9.0.1 Confluence Data Center e Server 10.2.x, versione 10.2.11 (LTS) e precedenti 10.1.x, versione 10.1.2 e precedenti 10.0.x, versione 10.0.3 e precedenti, da 10.0.2 9.5.x, versione 9.5.4 e precedenti, da 9.5.1 9.4.x, versione 9.4.1 e precedenti 9.3.x, versione 9.3.2 e precedenti, da 9.3.1 9.2.x, versione 9.2.20 (LTS) e precedenti 9.1.x, versione 9.1.1 e precedenti 9.0.x, versione 9.0.3 e precedenti, da 9.0.1 8.9.x, versione 8.9.8 e precedenti, da 8.9.4 8.5.x, versione 8.5.31 (LTS) e precedenti, da 8.5.12 7.19.x, versione 7.19.30 (LTS) e precedenti, da 7.19.25 Crowd Data Center e Server 7.2.x, versione 7.2.0 7.1.x, versione 7.1.5 e precedenti 7.0.x, versione 7.0.2 e precedenti 6.3.x, versione 6.3.6 e precedenti 6.2.x, versione 6.2.6 e precedenti 6.1.x, versione 6.1.7 e precedenti 6.0.x, versione 6.0.10 e precedenti 5.3.x, versione 5.3.8 e precedenti, da 5.3.2 Jira Data Center e Server 11.3.x, versione 11.3.6 (LTS) e precedenti 11.2.x, versione 11.2.1 e precedenti 11.1.x, versione 11.1.1 e precedenti 11.0.x, versione 11.0.1 e precedenti 10.7.x, versione 10.7.4 e precedenti, da 10.7.1 10.6.x, versione 10.6.1 e precedenti 10.5.x, versione 10.5.1 e precedenti 10.4.x, versione 10.4.1 e precedenti 10.3.x, versione 10.3.21 (LTS) e precedenti 10.2.x, versione 10.2.1 e precedenti 10.1.x, versione 10.1.2 e precedenti, da 10.1.1 10.0.x, versione 10.0.1 e precedenti 9.17.x, versione 9.17.5 e precedenti 9.12.x, versione 9.12.35 (LTS) e precedenti, da 9.12.11 Jira Service Management Data Center e Server 11.3.x, versione 11.3.6 (LTS) e precedenti 11.2.x, versione 11.2.1 e precedenti 11.1.x, versione 11.1.1 e precedenti 11.0.x, versione 11.0.1 e precedenti 10.7.x, versione 10.7.4 e precedenti, da 10.7.1 10.6.x, versione 10.6.1 e precedenti 10.5.x, versione 10.5.1 e precedenti 10.4.x, versione 10.4.1 e precedenti 10.3.x, versione 10.3.21 (LTS) e precedenti 10.2.x, versione 10.2.1 e precedenti 10.1.x, versione 10.1.2 e precedenti, da 10.1.1 10.0.x, versione 10.0.1 e precedenti 5.17.x, versione 5.17.5 e precedenti Azioni di mitigazione In linea con le dichiarazioni del vendor, si raccomanda di aggiornare i prodotti vulnerabili seguendo le indicazioni dei bollettini di sicurezza riportati nella sezione Riferimenti. Di seguito sono riportate le sole CVE relative alle vulnerabilità con gravità “critica” e “alta”. Data pubblicazione 18/06/26 ore 16:17 Data Ultimo Aggiornamento 18/06/26 ore 16:17
acn.gov.itJun 18, 2026extracted
Atlassian, Splunk Patch Critical Vulnerabilities
Atlassian and Splunk on Wednesday announced patches for multiple vulnerabilities in their products, including critical-severity flaws. Splunk resolved a critical issue in AI Toolkit that could allow authenticated attackers with admin roles to execute arbitrary OS commands on the host the Splunk Enterprise instance runs on. “The vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation,” Splunk explains. Tracked as CVE-2026-20266 (CVSS score of 9.1), the security defect was addressed in Splunk AI Toolkit version 5.7.4. If upgrading is not possible, Splunk recommends uninstalling the AI Toolkit as a mitigation. The update also addresses CVE-2026-20265, a medium-severity information disclosure bug caused by an insecure default domain allowlist. An attacker holding the admin or power role could cause the AI Toolkit to make outbound HTTP requests to attacker-controlled servers, leading to data exfiltration. Atlassian published 100 security bulletins that address dozens of security defects across Bamboo Data Center and Server, Bitbucket Data Center and Server, Confluence Data Center and Server, Crowd Data Center and Server, Fisheye/Crucible, Jira Data Center and Server, and Jira Service Management Data Center and Server. All the weaknesses resolved with the fresh security updates appear to affect third-party dependencies used in Atlassian’s products. These include critical-severity issues in Axios (CVE-2026-42043, CVE-2026-40175, and CVE-2026-42264), Apache Tomcat (CVE-2026-41293, CVE-2026-43512, CVE-2026-41293, CVE-2026-43515, and CVE-2026-43515), and Netty (CVE-2026-42584). Users are advised to update to a patched version of the affected Atlassian products as soon as possible. Related: Critical Command Execution Vulnerability Patched in Cisco ISE Related: F5 Patches Critical, High-Severity NGINX Vulnerabilities Related: Microsoft Working on Patch for ‘RoguePlanet’ Zero-Day Related: 3 Recently Patched Fortinet FortiSandbox Vulnerabilities in Hacker Crosshairs
securityweek.comJun 18, 2026extracted
Risolte vulnerabilità in prodotti Atlassian
Risolte vulnerabilità in prodotti Atlassian Alert AL07/260521/CSIRT-ITA Sintesi Rilasciati aggiornamenti di sicurezza per risolvere alcune vulnerabilità di cui 2 con gravità “critica” e 8 con gravità “alta” presenti nei prodotti Bamboo, Jira, Bitbucket, Confluence, nelle versioni Data Center e Server e Fisheye/Crucible di Atlassian. Tali vulnerabilità, qualora sfruttate, potrebbero consentire ad un utente malintenzionato remoto l’accesso ad informazioni sensibili, di compromettere l‘integrità delle informazioni e la disponibilità del servizio, nonché di eseguire codice arbitrario sui sistemi interessati. Tipologia Remote Code Execution Denial of Service Information Disclosure Data Manipulation Security Feature Bypass Prodotti e/o versioni affette Bamboo Data Center e Server 12.1.x, versione 12.1.6 (LTS) e precedenti 12.0.x, versione 12.0.2 e precedenti 11.0.x, versione 11.0.8 e precedenti 10.2.x, versione 10.2.18 (LTS) e precedenti 10.1.x, versione 10.1.1 e precedenti 10.0.x, versione 10.0.3 e precedenti 9.6.x, versione 9.6.25 (LTS) e precedenti Bitbucket Data Center e Server 10.2.x, versione 10.2.1 (LTS) e precedenti 10.1.x, versione 10.1.5 e precedenti 10.0.x, versione 10.0.2 e precedenti 9.6.x, versione 9.6.5 e precedenti 9.5.x, versione 9.5.2 e precedenti 9.4.x, versione 9.4.18 e precedenti 9.3.x, versione 9.3.2 e precedenti 9.2.x, versione 9.2.1 e precedenti 9.1.x, versione 9.1.1 e precedenti 9.0.x, versione 9.0.1 e precedenti 8.19.x, versione 8.19.29 (LTS) e precedenti Confluence Data Center e Server 10.2.x, versione 10.2.10 (LTS) e precedenti 10.1.x, versione 10.1.2 e precedenti 10.0.x, versioni comprese tra 10.0.2 e 10.0.3 9.5.x, versioni comprese tra 9.5.1 e 9.5.4 9.4.x, versione 9.4.1 e precedenti 9.3.x, versioni comprese tra 9.3.1 e 9.3.2 9.2.x, versione 9.2.19 e precedenti 9.1.x, versione 9.1.1 e precedenti 9.0.x, versioni comprese tra 9.0.1 e 9.0.3 8.9.x, versioni comprese tra 8.9.2 e 8.9.8 Fisheye/Crucible 4.9.x, versione 4.9.9 e precedenti Jira Data Center e Server 11.3.x, versione 11.3.4 (LTS) e precedenti 11.2.x, versione 11.2.1 e precedenti 11.1.x, versione 11.1.1 e precedenti 11.0.x, versione 11.0.1 e precedenti 10.7.x, versioni comprese tra 10.7.1 e 10.7.4 10.6.x, versione 10.6.1 e precedenti 10.5.x, versione 10.5.1 e precedenti 10.4.x, versione 10.4.1 e precedenti 10.3.x, versione 10.3.19 (LTS) e precedenti 10.2.x, versione 10.2.1 e precedenti 10.1.x, versioni comprese tra 10.1.1 e 10.1.2 10.0.x, versione 10.0.1 e precedenti 9.17.x, versione 9.17.5 e precedenti 9.16.x, versione 9.16.1 e precedenti 9.12.x, versioni comprese tra 9.12.32 e 9.12.34 (LTS) Jira Service Management Data Center e Server 11.3.x, versione 11.3.4 (LTS) e precedenti 11.2.x, versione 11.2.1 e precedenti 11.1.x, versione 11.1.1 e precedenti 11.0.x, versione 11.0.1 e precedenti 10.7.x, versioni comprese tra 10.7.1 e 10.7.4 10.6.x, versione 10.6.1 e precedenti 10.5.x, versione 10.5.1 e precedenti 10.4.x, versione 10.4.1 e precedenti 10.3.x, versione 10.3.19 (LTS) e precedenti 10.2.x, versione 10.2.1 e precedenti 10.1.x, versioni comprese tra 10.1.1 e 10.1.2 10.0.x, versione 10.0.1 e precedenti 5.17.x, versione 5.17.5 e precedenti 5.16.x, versione 5.16.1 e precedenti Azioni di mitigazione In linea con le dichiarazioni del vendor, si raccomanda di aggiornare i prodotti vulnerabili seguendo le indicazioni dei bollettini di sicurezza riportati nella sezione Riferimenti. Di seguito sono riportate le sole CVE relative alle vulnerabilità con gravità “critica” e “alta”. Data pubblicazione 21/05/26 ore 17:25 Data Ultimo Aggiornamento 21/05/26 ore 17:25
acn.gov.itMay 21, 2026extracted
North Korean Hackers Abuse VS Code Auto-Run Tasks to Deploy StoatWaffle Malware
The North Korean threat actors behind the Contagious Interview campaign, also tracked as WaterPlum, have been attributed to a malware family tracked as StoatWaffle that's distributed via malicious Microsoft Visual Studio Code (VS Code) projects. The use of VS Code "tasks.json" to distribute malware is a relatively new tactic adopted by the threat actor since December 2025, with the attacks leveraging the "runOn: folderOpen" option to automatically trigger its execution every time any file in the project folder is opened in VS Code. "This task is configured so that it downloads data from a web application on Vercel regardless of executing OS [operating system]," NTT Security said in a report published last week. "Though we assume that the executing OS is Windows in this article, the essential behaviors are the same for any OS." The downloaded payload first checks whether Node.js is installed in the executing environment. If it's absent, the malware downloads Node.js from the official website and installs it. Subsequently, it proceeds to launch a downloader, which periodically polls an external server to fetch a next-stage downloader that exhibits identical behavior by reaching out to another endpoint on the same server and executing the received response as Node.js code. StoatWaffle has been found to deliver two different modules - A stealer that captures credentials and extension data stored in web browsers (Chromium-based browsers and Mozilla Firefox) and uploads them to a command-and-control (C2) server. If the compromised system runs on macOS, it also steals the iCloud Keychain database. A remote access trojan (RAT) that communicates with the C2 server to fetch and execute commands on the infected host. The commands allow the malware to change the current working directory, enumerate files and directories, execute Node.js code, upload file, recursively search the given directory and list or upload files matching a certain keyword, run shell commands, and terminate itself. "StoatWaffle is a modular malware implemented by Node.js, and it has Stealer and RAT modules," the Japanese security vendor said. "WaterPlum is continuously developing new malware and updating existing ones." The development coincides with various campaigns mounted by the threat actor targeting the open-source ecosystem - A set of malicious npm packages that distribute the PylangGhost malware, marking the first time the Python-based backdoor has been propagated via npm packages. A campaign known as PolinRider has implanted a malicious obfuscated JavaScript payload in hundreds of public GitHub repositories that culminates in the deployment of a new version of BeaverTail, a known stealer and downloader malware attributed to Contagious Interview. Among the compromises are four repositories belonging to the Neutralinojs GitHub organization. The attack is said to have compromised the GitHub account of a long-time neutralinojs contributor with organization-level write access to force-push JavaScript code that retrieves encrypted payloads in Tron, Aptos, and Binance Smart Chain (BSC) transactions to download and run BeaverTail. The victims are believed to have been infected via a malicious VS Code extension or an npm package. Microsoft, in an analysis of Contagious Interview this month, said the threat actors achieve initial access to developer systems through "convincingly staged recruitment processes" that mirror legitimate technical interviews, ultimately persuading victims into running malicious commands or packages hosted on GitHub, GitLab, or Bitbucket as part of the assessment. In some cases, targets are approached on LinkedIn. However, the individuals chosen for this social engineering attack are not junior developers, but rather founders, CTOs, and senior engineers in the cryptocurrency or Web3 sector, who are likely to have elevated access to the company's tech infrastructure and cryptocurrency wallets. A recent incident involved the attackers unsuccessfully targeting the founder of AllSecure.io via a fake job interview. The hacking group is known to create fake LinkedIn company pages to lend credibility to the attacks, and set up GitHub accounts for malware delivery. Some attacks have also leveraged a popular social engineering tactic known as ClickFix to distribute malware like PylangGhost via bogus skills assessment tasks. Additionally, the threat actor has a history of publishing malicious packages to the npm registry. "While these attacks appear to have a central goal of cryptocurrency theft, the threat group has demonstrated its intention to use initial access for further supply chain compromise or corporate espionage," Sophos said, noting that the adversary strategically selects follow-on payloads after profiling victims' systems. The cybersecurity vendor is tracking the activity under the name Nickel Alley. Some of the key malware families deployed as part of these attack chains include OtterCookie (a backdoor capable of extensive data theft), InvisibleFerret (a Python-based backdoor), and FlexibleFerret (a modular backdoor implemented in both Go and Python). While InvisibleFerret is known to be typically delivered via BeaverTail, recent intrusions have been found to distribute the malware as a follow-on payload, after leveraging initial access obtained through OtterCookie. It's worth mentioning here that FlexibleFerret is also referred to as WeaselStore. Its Go and Python variants go by the monikers GolangGhost and PylangGhost, respectively. In a sign that the threat actors are actively refining their tradecraft, newer mutations of the VS Code projects have eschewed Vercel-based domains for GitHub Gist-hosted scripts to download and execute next-stage payloads that ultimately lead to the deployment of FlexibleFerret. These VS Code projects are staged on GitHub. "By embedding targeted malware delivery directly into interview tools, coding exercises, and assessment workflows developers inherently trust, threat actors exploit the trust job seekers place in the hiring process during periods of high motivation and time pressure, lowering suspicion and resistance," the tech giant said. In response to the ongoing abuse of VS Code Tasks, Microsoft has included a mitigation in the January 2026 update (version 1.109) that introduces a new "task.allowAutomaticTasks" setting, which defaults to "off" in order to improve security and prevent unintended execution of tasks defined in "tasks.json" when opening a workspace. "The update also prevents the setting from being defined at the workspace level, so malicious repositories with their own .vscode/settings.json file should not be able to override the user (global) setting," Abstract Security said. "This version and the recent February 2026 (version 1.110) release also introduce a secondary prompt that warns the user when an auto-run task is detected in a newly opened workspace. This acts as an additional guard after a user accepts the Workspace Trust prompt." In recent months, North Korean threat actors have also been engaging in a coordinated malware campaign targeting cryptocurrency professionals through LinkedIn social engineering, fake venture capital firms, and fraudulent video conferencing links. The activity shares overlap with clusters tracked as GhostCall and UNC1069. "The attack chain culminates in a ClickFix-style fake CAPTCHA page that tricks victims into executing clipboard-injected commands in their Terminal," MacPaw's Moonlock Lab said. "The campaign is cross-platform by design, delivering tailored payloads for both macOS and Windows." The findings come as the U.S. Department of Justice (DoJ) announced the sentencing of three men -- Audricus Phagnasay, 25, Jason Salazar, 30, and Alexander Paul Travis, 35 -- for their roles in furthering North Korea's fraudulent information technology (IT) worker scheme in violation of international sanctions. All three individuals previously pleaded guilty in November 2025. Phagnasay and Salazar were both sentenced to three years of probation and a $2,000 fine. They were also ordered to forfeit the illicit proceeds gained by participating in the wire fraud conspiracy. Travis was sentenced to one year in prison and ordered to forfeit $193,265, the amount earned by North Koreans by using his identity. "These men practically gave the keys to the online kingdom to likely North Korean overseas technology workers seeking to raise illicit revenue for the North Korean government — all in return for what to them seemed like easy money," Margaret Heap, U.S. attorney for the Southern District of Georgia, said in a statement. Last week, Flare and IBM X-Force published a detailed look at the IT worker operation and its internal structure, while highlighting how IT workers attend prestigious universities in North Korea and go through a rigorous interview process themselves before joining the scheme. They are "considered elite members of North Korean society and have become an indispensable part of the overall North Korean government's strategic objectives," the companies noted. "These objectives include, but are not limited to, revenue generation, remote employment activity, theft of corporate and proprietary information, extortion, and providing support to other North Korean groups."
thehackernews.comMar 23, 2026extracted
New infosec products of the month: February 2026
New infosec products of the month: February 2026 Here’s a look at the most interesting products from the past month, featuring releases from Aikido Security, Avast, Armis, Black Duck, Compliance Scorecard, Fingerprint, Gremlin, Impart Security, Portnox, Redpanda, Socure, SpecterOps, Veza, and Virtana. Gremlin launches Disaster Recovery Testing for zone, region, and datacenter failovers Gremlin, the proactive reliability platform, launched Disaster Recovery Testing: a new product built to safely and efficiently test zone, region, and datacenter evacuations and failovers. These large-scale tests ensure businesses maintain digital resilience and business continuity when faced with cloud migrations, compliance concerns, and catastrophic events. Fingerprint enables enterprises to tell trusted AI agents apart from bots and scrapers Fingerprint has released Authorized AI Agent Detection, its new ecosystem of AI agents, including OpenAI, AWS AgentCore, Browserbase, Manus and Anchor Browser. The ecosystem enables enterprises to detect authorized agentic AI traffic with 100% certainty, allowing organizations to distinguish trusted, permissioned automation from malicious bots and scrapers. Socure unifies identity, fraud, and program integrity for government at scale Socure has released Socure for Government (SocureGov) RiskOS to help public sector organizations deliver simpler, faster, and more transparent digital identity verification and fraud prevention at scale. Avast brings deepfake scam detection to Windows PCs and mobile devices Avast announced the full international availability of Avast Scam Guardian and Scam Guardian Pro on mobile devices, alongside the launch of Avast Deepfake Guard on Windows PCs, a new AI-powered feature designed to proactively analyze and detect malicious audio in video content. Together, these launches expand the Avast scam protection ecosystem, extending coverage across mobile and PC to help protect people from scams across text messages, calls, and video platforms. Armis Centrix brings unified, AI-driven application security to the SDLC Armis has announced Armis Centrix for Application Security, which unifies application security across an organization’s software development lifecycle. The technology helps security teams secure code as a next-generation attack vector to fortify organizations’ defenses and protect against cyber threats. BloodHound Scentry helps organizations reduce identity risk and close attack paths SpecterOps has announced BloodHound Scentry, a new service designed to help customers accelerate their APM practice and reduce identity risk. BloodHound Scentry combines the power of BloodHound Enterprise with SpecterOps tradecraft experts and practitioners to provide customers with tailored guidance for attack path remediation, advanced analysis for emerging threats, and privilege zone design to protect critical assets. Portnox expands ZTNA with passwordless access for RDP, SSH, and enterprise consoles Portnox has unveiled a major expansion of its zero trust network access (ZTNA) solution, extending credential-free access beyond web and on-premises applications to include enterprise console-based applications. Black Duck expands Polaris platform with unified, automated security across all major SCMs Black Duck has announced the availability of a set of enhanced Black Duck Polaris Platform integrations across all major source code management (SCM) platforms, including GitHub, GitLab, Azure DevOps, and Bitbucket. The Polaris Platform is an integrated, software-as-a-service application security platform powered by the static application security testing, software composition analysis, and dynamic application security testing engines. Impart enables safe, in-app enforcement against AI-powered bots Impart Security has launched Programmable Bot Protection, a runtime approach to bot defense that brings detection and enforcement together within the application. Impart makes enforcement operational by enabling teams to see what would be blocked before turning it on. Compliance Scorecard v10 delivers context-driven AI for explainable compliance decisions Compliance Scorecard announced the release of v10, introducing governed, audit-ready AI designed to support defensible compliance decision-making for managed service providers (MSPs). Compliance Scorecard v10 applies AI only within a structured system of validated context and controls. The platform is built on a simple premise: AI can only be trusted in compliance if the required context already exists. As a result, v10 treats AI as a governed system of decision support, not a conversational interface. Virtana expands MCP Server to bring full-stack enterprise context to AI agents Virtana announced the latest version of its Model Context Protocol (MCP) Server, bringing full-stack enterprise visibility directly to AI agents and LLMs so machines can understand enterprise operations as complete systems rather than isolated signals. Redpanda brings identity, policy control, and data governance to AI agents Redpanda announced the availability of new core capabilities in the Redpanda Agentic Data Plane (ADP), including a centralized AI gateway, AI observability and evaluation via OpenTelemetry, AI agents, and unified authentication and authorization. Together, these features form a unified governance layer that allows enterprises to securely connect AI agents and Model Context Protocol (MCP) servers to live enterprise data with visibility and control. Aikido Infinite introduces continuous, self-remediating AI penetration testing Aikido Security has unveiled Aikido Infinite, a continuous AI penetration testing solution that autonomously validates and remediates vulnerabilities. Infinite reduces risk with every release by testing software changes as they move through deployment, confirming exploitability, and fixing vulnerabilities within the same workflow. Veza expands platform with AI Access Agents for enterprise identity governance Veza expanded its platform with Veza Access Agents, a set of purpose-built AI agents designed to automate complex identity and access governance tasks for enterprises. Veza also announced advancements to its AI Agent Security product, providing organizations with deeper visibility into agent risks and greater control over third-party AI agents, large language models (LLMs), AI apps, and AI infrastructure (MCP).
helpnetsecurity.comFeb 27, 2026extracted
Microsoft Warns Developers of Fake Next.js Job Repos Delivering In-Memory Malware
A "coordinated developer-targeting campaign" is using malicious repositories disguised as legitimate Next.js projects and technical assessments to trick victims into executing them and establish persistent access to compromised machines. "The activity aligns with a broader cluster of threats that use job-themed lures to blend into routine developer workflows and increase the likelihood of code execution," the Microsoft Defender Security Research Team said in a report published this week. The tech giant said the campaign is characterized by the use of multiple entry points that lead to the same outcome, where attacker-controlled JavaScript is retrieved at runtime and executed to facilitate command-and-control (C2). The attacks rely on the threat actors setting up fake repositories on trusted developer platforms like Bitbucket, using names like "Cryptan-Platform-MVP1" to trick developers looking for jobs into running them as part of an assessment process. Further analysis of the identified repositories has uncovered three distinct execution paths that, while triggered in different ways, have the end goal of executing an attacker‑controlled JavaScript directly in memory - Visual Studio Code workspace execution, where Microsoft Visual Studio Code (VS Code) projects with workspace automation configuration are used to run malicious code retrieved from a Vercel domain as soon as the developer opens and trusts the project. This involves the use of the runOn: "folderOpen" to configure the task. Build‑time execution during application development, where manually running the development server via "npm run dev" is enough to activate the execution of malicious code embedded within modified JavaScript libraries masquerading as jquery.min.js, causing it to fetch a JavaScript loader hosted on Vercel. The retrieved payload is then executed in memory by Node.js. Server startup execution via environment exfiltration and dynamic remote code execution, where launching the application backend causes malicious loader logic concealed within a backend module or route file to be executed. The loader transmits the process environment to the external server and executes JavaScript received as a response in memory within the Node.js server process. Microsoft noted that all three methods lead to the same JavaScript payload that's responsible for profiling the host and periodically polling a registration endpoint to get a unique "instanceId" identifier. This identifier is subsequently supplied in follow-on polls to correlate activity. It's also capable of executing server-provided JavaScript in memory, ultimately paving the way for a second-stage controller that turns the initial foothold into a persistent access pathway for receiving tasks by contacting a different C2 server and executing them in memory to minimize leaving traces on disk. "The controller maintains stability and session continuity, posts error telemetry to a reporting endpoint, and includes retry logic for resilience," Microsoft said. "It also tracks spawned processes and can stop managed activity and exit cleanly when instructed. Beyond on-demand code execution, Stage 2 supports operator-driven discovery and exfiltration." While the Windows maker did not attribute the activity to a specific threat actor, the use of VS Code tasks and Vercel domains to stage malware is a tactic that has been adopted by North Korea-linked hackers associated with a long-running campaign known as Contagious Interview. The end goal of these efforts is to gain the ability to deliver malware to developer systems, which often contain sensitive data, such as source code, secrets, and credentials, that can provide opportunities to pivot deeper into the target network. In a report published Wednesday, Abstract Security said it has observed a shift in threat actor tactics, notably a spike in alternative staging servers used in the VS Code tasks commands instead of Vercel URLs. This includes the use of scripts hosted on GitHub gists ("gist.githubusercontent[.]com") to download and run next-stage payloads. An alternative approach employs URL shorteners like short[.]gy to conceal Vercel URLs. The cybersecurity company said it also identified a malicious npm package, named "eslint-validator," linked to the campaign that retrieves and runs an obfuscated payload from a Google Drive URL. The payload in question is a known JavaScript malware referred to as JADESNOW. Furthermore, a malicious VS Code task embedded within a GitHub repository has been found to initiate a Windows-only infection chain that runs a batch script to download Node.js runtime on the host (if it does not exist) and leverage the certutil program to parse a code block contained within the script. The decoded script is then executed with the previously obtained Node.js runtime to deploy a Python malware protected with PyArmor. The Python payload is assessed to be a Go-based variant of Akira Stealer, an off-the-shelf malware-as-a-service (MaaS) infostealer that harvests user data from browsers, cryptocurrency wallets, chat applications, and system files. The use of Akira Stealer, Abstract Security, said complicates attribution efforts as the stealer is not known to be used by Contagious Interview actors. "It is possible that this is a separate actor copying techniques and swapping in a different final stage," the company told The Hacker News. "As such, this chain's attribution remains uncertain [despite] the shared techniques and infection vector." Cybersecurity company Red Asgard, which has also been extensively tracking the campaign, said the threat actors have leveraged crafted VS code projects that use the runOn: "folderOpen" trigger to deploy malware that, in turn, queries the Polygon blockchain to retrieve JavaScript stored within an NFT contract for improved resilience. The final payload is an information stealer that harvests credentials and data from web browsers, cryptocurrency wallets, and password managers. "This developer‑targeting campaign shows how a recruiting‑themed 'interview project' can quickly become a reliable path to remote code execution by blending into routine developer workflows such as opening a repository, running a development server, or starting a backend," Microsoft concluded. To counter the threat, the company is recommending that organizations harden developer workflow trust boundaries, enforce strong authentication and conditional access, maintain strict credential hygiene, apply the principle of least privilege to developer accounts and build identities, and separate build infrastructure where feasible. The development comes as GitLab said it banned 131 unique accounts in 2025 that were engaged in distributing malicious code projects linked to the Contagious Interview campaign and the fraudulent IT worker scheme known as Wagemole. "Threat actors typically originated from consumer VPNs when interacting with GitLab.com to distribute malware; however, they also intermittently originated from dedicated VPS infrastructure and likely laptop farm IP addresses," GitLab's Oliver Smith said. "Threat actors created accounts using Gmail email addresses in almost 90% of cases." In more than 80% of the cases, per the software development platform, the threat actors are said to have leveraged at least six legitimate services to host malware payloads, including JSON Keeper, Mocki, npoint.io, Render, Railway.app, and Vercel. Among these, Vercel was the most commonly used, with the threat actors relying on the web development platform no less than 49 times in 2025. "In December, we observed a cluster of projects executing malware via VS Code tasks, either piping remote content to a native shell or executing a custom script to decode malware from binary data in a fake font file," Smith added, corroborating the aforementioned findings from Microsoft. Also discovered by GitLab was a private project "almost certainly" controlled by a North Korean national managing a North Korean IT worker cell that contained detailed financial and personnel records showing earnings of more than $1.64 million between Q1 2022 and Q3 2025. The project included more than 120 spreadsheets, presentations, and documents tracking quarterly income performance for individual team members. "Records demonstrate that these operations function as structured enterprises with defined targets and operating procedures and close hierarchical oversight," GitLab noted. "This cell's demonstrated ability to cultivate facilitators globally provides a high degree of operational resiliency and money laundering flexibility." In a report published earlier this month, Okta said the "vast majority" of interviews with IT workers do not progress to a second interview or job offer, but noted they are "learning from their mistakes" and that a large number of them seek temporary contract work as software developers hired out to third-party companies to take advantage of the fact that they are unlikely to enforce rigorous background checks. "Some actors however seem to be more competent at crafting personas and passing screening interviews," it added. "A kind of IT Worker natural selection is at play. The most successful actors are very prolific, and scheduled hundreds of interviews each."
thehackernews.comFeb 26, 2026extracted
Fake Next.js job interview tests backdoor developer's devices
A coordinated campaign targeting software developers with job-themed lures is using malicious repositories posing as legitimate Next.js projects and technical assessment materials, including recruiting coding tests. The attacker's goal is to achieve remote code execution (RCE) on developer machines, exfiltrate sensitive data, and introduce additional payloads on compromised systems. Multiple execution triggers Next.js is a popular JavaScript framework used for building web applications. It runs on top of React and uses Node.js for the backend. The Microsoft Defender team says that the attacker created fake web app projects built with Next.js and disguised them as coding projects to share with developers during job interviews or technical assessments. The researchers initially identified a repository hosted on the Bitbucket cloud-based Git-based code hosting and collaboration service. However, they discovered multiple repositories that shared code structure, loader logic, and naming patterns. When the target clones the repository and opens it locally, following a standard workflow, they trigger malicious JavaScript that executes automatically when launching the app. The script downloads additional malicious code (a JavaScript backdoor) from the attacker's server and executes it directly in memory with the running Node.js process, allowing remote code execution on the machine. To increase the infection rate, the attackers embedded multiple execution triggers within the malicious repositories, Microsoft explained. These are summarized as follows: VS Code trigger – A .vscode/tasks.json file set with runOn: "folderOpen" executes a Node script as soon as the project folder is opened (and trusted). Dev server trigger – When the developer runs npm run dev, a trojanized asset (e.g., a modified JS library) decodes a hidden URL, fetches a loader from a remote server, and executes it in memory. Backend startup trigger – On server start, a backend module decodes a base64 endpoint from .env, sends process.env to the attacker, receives JavaScript in response, and executes it using new Function(). The infection process drops a JavaScript payload (Stage 1) that profiles the host and registers with a command-and-control (C2) endpoint, polling the server at fixed intervals. The infection then upgrades to a tasking controller (Stage 2) that connects to a separate C2 server, checks for tasks, executes supplied JavaScript in memory, and tracks spawned processes. The payload also supports file enumeration, directory browsing, and staged file exfiltration. Microsoft found that the campaign involved multiple repositories that shared naming conventions, loader structure, and staging infrastructure, indicating a coordinated effort rather than a one-off attack. Aside from the technical analysis, the researchers did not provide any details about the attacker or the extent of the operation. The tech giant advises that developers should treat standard workflows as the high-risk attack surfaces they really are and take appropriate precautions. The recommended mitigations include enforcing VS Code Workspace Trust/Restricted Mode, using Attack Surface Reduction (ASR) rules, and monitoring risky sign-ins with Entra ID Protection. Secrets stored on developer endpoints should be minimized, and short-lived tokens with the least required privileges should be used where possible. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comFeb 25, 2026extracted
Black Duck expands Polaris platform with unified, automated security across all major SCMs
Black Duck expands Polaris platform with unified, automated security across all major SCMs Black Duck has announced the availability of a set of enhanced Black Duck Polaris Platform integrations across all major source code management (SCM) platforms, including GitHub, GitLab, Azure DevOps, and Bitbucket. The Polaris Platform is an integrated, software-as-a-service application security platform powered by the static application security testing, software composition analysis, and dynamic application security testing engines. With development teams managing an explosion of human and AI-generated code and increasingly distributed development environments, manual onboarding and fragmented security tools create serious coverage gaps. These enhanced Polaris capabilities enable organizations to achieve unprecedented speed, coverage, and automation in securing their applications at scale. Designed for enterprises managing hundreds and even thousands of code repositories across globally distributed teams, these integrations simplify onboarding, accelerate scanning workflows, and seamlessly embed security into day-to-day development activities. Together, these enhancements reduce administrative overhead, eliminate manual configuration, and ensure continuous coverage for fast-changing codebases. Key features and benefits: Unified coverage across all major SCMs. Whether teams use GitHub, GitLab, Azure DevOps, Bitbucket, or a mix of all four, the natively built integration with the Polaris Platform provides a consistent, unified security experience, not a scripted add-on. Instant onboarding for thousands of repositories. Organizations can automatically onboard and continuously synchronize Polaris with every repository in their SCMs without the need for manual configuration. Continuous monitoring of repository changes. New repositories, renamed projects, branch creation, and other structural changes are detected instantly, ensuring security coverage always remains current and complete. Trigger scans on key development events. Polaris scans can be triggered automatically when a pull request is created/updated or before it is merged, allowing developers to catch and fix vulnerabilities during their normal code review process, resulting in vulnerabilities being addressed earlier in the SDLC. Apply AI‑powered application security with Black Duck Signal. Enabling scans directly in the IDE or automated through CI/CD, all centrally managed in Polaris. Signal surfaces meaningful security insights in both human‑ and AI‑generated code, helping teams stop vulnerabilities before code is committed. Extend security and AI insights directly to the developer’s desktop with Code Sight. This IDE plugin triggers Polaris scans, manually or automatically, while developers code. Combined with Black Duck Assist’s AI‑driven guidance and remediation, developers get immediate, actionable feedback, reducing friction and preventing rework later in the lifecycle. Customizable scanning with full or rapid analysis. Teams can choose between deep, comprehensive scanning or rapid analysis based on the context of each workflow. Seamless integration into developer workflows. Security findings surface directly inside pull requests, enabling developers to fix issues in real time, without switching tools or breaking flow. Instant policy onboarding. Enterprise security policies and guardrails can be enabled with a single click, ensuring consistent enforcement across thousands of repositories. Instant user onboarding. Teams, roles, and access controls synchronize automatically, reducing administrative overhead and accelerating time to value. “Enterprises are orchestrating software projects across hundreds and thousands of source code repositories in the race to adopt AI in production,” said Dipto Chakravarty, Chief Product and Technology Officer at Black Duck. “Development and Security teams need application security that is integrated, automated, and frictionless across their platforms and code repositories. No other solution combines the breadth of SCM platform support with universal event and policy-based automation, and the depth of analysis and agentic AI scalability provided by the Black Duck Polaris Platform. This is a game changer for operating DevSecOps at enterprise scale.”
helpnetsecurity.comFeb 12, 2026extracted
Atlassian Patches Critical Apache Tika Flaw
Atlassian has rolled out patches for roughly 30 third-party vulnerabilities impacting its products, including critical-severity flaws. The first security defect that stands out is CVE-2025-66516 (CVSS score of 10/10), a critical-severity XML External Entity (XXE) injection bug in Apache Tika. Impacting the tika-core, tika-pdf-module, and tika-parsers modules of the universal parser, the flaw was disclosed in early December. It can be exploited via crafted XFA files placed inside PDF files, potentially leading to information leaks, denial-of-service (DoS), SSRF attacks, or remote code execution (RCE). Atlassian products that use Tika include Bamboo, Confluence, Crowd, Fisheye/Crucible, Jira, and Jira Service Management. The company has released fixes for all six. The list of critical-severity issues that Atlassian resolved this month also includes CVE-2022-37601 (CVSS score of 9.8), a prototype pollution vulnerability in webpack loader-utils, which is used in Confluence. Another critical prototype pollution bug was patched in Jira and Jira Service Management. Tracked as CVE-2021-39227 (CVSS score of 9.8), it affects the lightweight graphic library ZRender. Atlassian’s fresh round of fixes also resolves over two dozen high-severity DoS, XXE, SSRF, file inclusion, prototype pollution, improper authorization, information disclosure, improper input validation, and RCE flaws. Software updates that fix these defects were released for Bamboo, Bitbucket, Confluence, Crowd, Fisheye/Crucible, Jira, and Jira Service Management data center and server products. Because the weaknesses were found in third-party dependencies, they impact all Atlassian products that rely on them. Users are advised to apply the patches as soon as possible. Additional information on the bugs and their fixes can be found in Atlassian’s December 2025 security advisory. Related: Gladinet CentreStack Flaw Exploited to Hack Organizations Related: Recent GeoServer Vulnerability Exploited in Attacks Related: Notepad++ Patches Updater Flaw After Reports of Traffic Hijacking Related: IBM Patches Over 100 Vulnerabilities
securityweek.comDec 15, 2025extracted
The hidden risks in your DevOps stack data—and how to address them
While DevOps drives innovation and simplifies collaboration, it also comes with its own set of risks and vulnerabilities. Developers rely on Git-based platforms like GitHub, Azure DevOps, Bitbucket, or GitLab to work on code. Repositories usually contain mission-critical data, and with growth, teams expand and their workflows get more complex — all leading to more potential risks that could affect your data. The Shared Responsibility model The division of duties in regards to SaaS data protection is outlined using platform-specific shared responsibility models. You, as a customer, are responsible for the data stored on your SaaS accounts. Platforms like GitHub are not obligated to help you with data recovery. The service provider is responsible for the uptime of their service, while the users’ duty is the security of data, accounts, and devices. That means users must implement strict access controls, protect credentials, and leverage automated backups; all to secure data against ransomware attacks, human errors like accidental deletions, and service disruptions. Moreover, SaaS platforms themselves advise their users to implement their own backups. Security differences between platforms The leading distributed VCS platforms, like GitLab, offer built-in security features. These can help with building a cyber defence strategy. The specific controls and tools differ in each platform and range from PATs to access controls and regular reviews. GitHub In GitHub, users get native controls that include secret scanning, push protection, code security features like dependency review, and Dependabot alerts. Push protection is on by default for new public repos, and it is blocking known secrets at push. Secret scanning is also enabled for all public repos and can be extended to private ones. It is advised to enforce MFA and branch protection across all projects. Bitbucket Bitbucket has hierarchical access, with team/group controls. Also, project-level permissions apply to all repos in that project unless they are tightened. Security largely depends on admins regularly reviewing group scopes and repo privacy. Bitbucket Secret Scanning feature helps with monitoring commits and pushes for exposed credentials. Make sure to configure pipeline variables and avoid exposing sensitive data. It’s worth noting that Bitbucket integrates with the suite of Atlassian tools and services, such as Jira. GitLab GitLab comes as a comprehensive DevSecOps platform, covering source code management, CI/CD, and security testing. Risks mainly come up in self-managed deployments where admins are responsible for hardening, patching, and backups. GitLab’s guidance in their documentation assigns patching and host security to self-managed customers. Be sure to implement strict role segregation and keep runners isolated. Azure DevOps Microsoft’s Azure DevOps integrates with identity management via Microsoft Entra ID (SSO, MFA, Conditional Access). A strong security posture for Azure DevOps data requires correctly configuring service connections and layered project/organization permissions. Microsoft emphasizes customer responsibility for Azure DevOps configuration according to the Shared Responsibility Model. Common DevOps security gaps & challenges The data, along with configurations, stored in platforms like Bitbucket, are essential for modern software development. Therefore, your source code is a great target for cyber attacks or insider threats. These bad actors demand ransom as they gain access to your data that business continuity and security rely on. It’s important to shift security to the left and address the industry-known vulnerabilities. Common vulnerabilities include: Weak access control Improper repository permissions and configurations No multi-factor authentication (MFA) or single sign-on (SSO) Outdated systems & workflows No automated backup (or treating GitHub, GitLab, Azure DevOps, or Bitbucket as backup) Lack of tested disaster recovery strategies Non-compliance with industry regulations For example, there was a supply-chain attack targeting a popular GitHub Action called ‘tj-actions/changed-files’. The attackers published a malicious update under the same package name that was used across thousands of repositories, potentially exposing repository data and CI/CD secrets. Attacks vectors There are different ways attackers can exploit vulnerabilities to access your data. They range from phishing and credential theft to ransomware attacks. Ransomware encrypts or erases your data — but how it is done depends on the platform: Accidental deletion Another risk is the potential for accidental deletions and malicious insiders doing damage from within the organization. This can be as simple as a mistyped command or excessive privileges leading to project deletion, but it can be devastating in the long run without backup or flexible recovery options. Malicious insiders can intentionally disrupt operations or disable logging. Both cases can result in lost repo history, costly recovery, erased & lost data, as well as paused business operations. Service outages Software development teams face service outages of critical platforms they rely on. Downtime means no access to important repositories and CI/CD pipelines, which could completely stop business operations. The consequences range from missed deadlines and a lack of customer trust to wasted resources. How to improve the security of your DevOps data To address all of the abovementioned risks and secure data on git-hosting platforms, organizations must shift security left, and adhere to compliance requirements of industry regulations. It is important to remember that secrets should never be stored in repositories. Access management Strict access control means implementing RBAC (Role-based access control) and following the principle of the least privilege. This way, permissions are adjusted specifically to each role and assigned accordingly, with no excessive access given to any user. All permissions should be verified regularly and inactive accounts revoked. Backup and disaster recovery A third-party backup and disaster recovery solution such as GitProtect is like a safety net. When choosing a solution, seek full coverage for your DevOps stack (project data, repositories, and all the metadata). Ideally, backups should be automated, encrypted, geo-redundant, and stored in WORM-compliant, immutable format. This should be completed by a flexible recovery arsenal: granular restore, cross-over recovery, point-in-time restore, and full data recovery. When backup and disaster recovery solutions check those boxes, you guarantee ransomware protection, compliance with industry standards, and adherence to the 3-2-1 backup rule. Other critical aspects include monitoring and audit preparedness, an intuitive user interface, along with alerts, notifications, and clear logs. Ensure compliant DevOps backup and recovery with a 14-day trial of GitProtect. No credit card required! Sponsored and written by GitProtect.
bleepingcomputer.comNov 19, 2025extracted
Researchers Expose GhostCall and GhostHire: BlueNoroff's New Malware Chains
Threat actors tied to North Korea have been observed targeting the Web3 and blockchain sectors as part of twin campaigns tracked as GhostCall and GhostHire. According to Kaspersky, the campaigns are part of a broader operation called SnatchCrypto that has been underway since at least 2017. The activity is attributed to a Lazarus Group sub-cluster called BlueNoroff, which is also known as APT38, CageyChameleon, CryptoCore, Genie Spider, Nickel Gladstone, Sapphire Sleet (formerly Copernicium), and Stardust Chollima. Victims of the GhostCall campaign span several infected macOS hosts located in Japan, Italy, France, Singapore, Turkey, Spain, Sweden, India, and Hong Kong, whereas Japan and Australia have been identified as the major hunting grounds for the GhostHire campaign. "GhostCall heavily targets the macOS devices of executives at tech companies and in the venture capital sector by directly approaching targets via platforms like Telegram, and inviting potential victims to investment-related meetings linked to Zoom-like phishing websites," Kaspersky researchers Sojun Ryu and Omar Amin said. "The victim would join a fake call with genuine recordings of this threat's other actual victims rather than deepfakes. The call proceeds smoothly to then encourages the user to update the Zoom client with a script. Eventually, the script downloads ZIP files that result in infection chains deployed on an infected host." On the other hand, GhostHire involves approaching prospective targets, such as Web3 developers, on Telegram and luring them into downloading and executing a booby-trapped GitHub repository under the pretext of completing a skill assessment within 30 minutes of sharing the link, so as to ensure a higher success rate of infection. Once installed, the project is designed to download a malicious payload onto the developer's system based on the operating system used. The Russian cybersecurity company said it has been keeping tabs on the two campaigns since April 2025, although it's assessed that GhostCall has been active since mid-2023, likely following the RustBucket campaign. RustBucket marked the adversarial collective's major pivot to targeting macOS systems, following which other campaigns have leveraged malware families like KANDYKORN, ObjCShellz, and TodoSwift. It's worth noting that various aspects of the activity have been documented extensively over the past year by multiple security vendors, including Microsoft, Huntress, Field Effect, Huntabil.IT, Validin, and SentinelOne. The GhostCall Campaign Targets who land on the fake Zoom pages as part of the GhostCall campaign are initially served a bogus page that gives the illusion of a live call, only to display an error message three to five seconds later, urging them to download a Zoom software development kit (SDK) to address a purported issue with continuing the call. Should the victims fall for the trap and attempt to update the SDK by clicking on the "Update Now" option, it leads to the download of a malicious AppleScript file onto their system. In the event the victim is using a Windows machine, the attack leverages the ClickFix technique to copy and run a PowerShell command. At each stage, every interaction with the fake site is recorded and beaconed to the attackers to track the victim's actions. As recently as last month, the threat actor has been observed transitioning from Zoom to Microsoft Teams, using the same tactic of tricking users into downloading a TeamsFx SDK this time to trigger the infection chain. Regardless of the lure used, the AppleScript is designed to install a phony application disguised as Zoom or Microsoft Teams. It also downloads another AppleScript dubbed DownTroy that checks stored passwords associated with password management applications and installs additional malware with root privileges. DownTroy, for its part, is engineered to drop several payloads as part of eight distinct attack chains, while also bypassing Apple's Transparency, Consent, and Control (TCC) framework - ZoomClutch or TeamsClutch, which uses a Swift-based implant that masquerades as Zoom or Teams while harboring functionality to prompt the user to enter their system password in order to complete the app update and exfiltrate the details to an external server DownTroy v1, which uses a Go-based dropper to launch the AppleScript-based DownTroy malware that's then responsible for downloading additional scripts from the server until the machine is rebooted. CosmicDoor, which uses a C++ binary loader called GillyInjector (aka InjectWithDyld) to run a benign Mach-O app and inject a malicious payload into it at runtime. When it's run with the --d flag, GillyInjector activates its destructive capabilities and irrevocably wipes all files in the current directory. The injected payload is a backdoor written in Nim named CosmicDoor that can communicate with an external server to receive and execute commands. It's believed that the attackers first developed a Go version of CosmicDoor for Windows, before moving to Rust, Python, and Nim variants. It also downloads a bash script stealer suite named SilentSiphon. RooTroy, which uses Nimcore loader to launch GillyInjector, which then injects a Go backdoor called RooTroy (aka Root Troy V4) to collect device information, enumerate running processes, read payload from a specific file, and download additional malware (counting RealTimeTroy) and execute them. RealTimeTroy, which uses Nimcore loader to launch GillyInjector, which then injects a Go backdoor called RealTimeTroy that communicates with an external server using the WSS protocol to read/write files, get directory and process information, upload/download files, terminate a specified process, and get device information. SneakMain, which uses Nimcore loader to launch a Nim payload called SneakMain to receive and execute additional AppleScript commands received from an external server. DownTroy v2, which uses a dropper named CoreKitAgent to launch Nimcore loader, which then launches AppleScript-based DownTroy (aka NimDoor) to download an additional malicious script from an external server. SysPhon, which uses a lightweight version of RustBucket named SysPhon and SUGARLOADER, a known loader previously utilized to deliver the KANDYKORN malware. SysPhon, also employed in the Hidden Risk campaign, is a downloader written in C++ that can conduct reconnaissance and fetch a binary payload from an external server. SilentSiphon is equipped to harvest data from Apple Notes, Telegram, web browser extensions, as well as credentials from browsers and password managers, and secrets stored in configuration files related to a long list of services: GitHub, GitLab, Bitbucket, npm, Yarn, Python pip, RubyGems, Rust cargo, NET Nuget, AWS, Google Cloud, Microsoft Azure, Oracle Cloud, Akamai Linode, DigitalOcean API, Vercel, Cloudflare, Netlify, Stripe, Firebase, Twilio, CircleCI, Pulumi, HashiCorp, SSH, FTP, Sui Blockchain, Solana, NEAR Blockchain, Aptos Blockchain, Algorand, Docker, Kubernetes, and OpenAI. "While the video feeds for fake calls were recorded via the fabricated Zoom phishing pages the actor created, the profile images of meeting participants appear to have been sourced from job platforms or social media platforms such as LinkedIn, Crunchbase, or X," Kaspersky said. "Interestingly, some of these images were enhanced with [OpenAI] GPT-4o." The GhostHire Campaign The GhostHire campaign, the Russian cybersecurity company added, also dates back to mid-2023, with the attackers initiating contact with the targets directly on Telegram, sharing details of a job offer along with a link to a LinkedIn profile impersonating recruiters at financial companies based in the U.S. in an attempt to lend the conversations a veneer of legitimacy. "Following up on initial communication, the actor adds the target to a user list for a Telegram bot, which displays the impersonated company’s logo and falsely claims to streamline technical assessments for candidates," Kaspersky explained. "The bot then sends the victim an archive file (ZIP) containing a coding assessment project, along with a strict deadline (often around 30 minutes) to pressure the target into quickly completing the task. This urgency increases the likelihood of the target executing the malicious content, leading to initial system compromise." The project in itself is innocuous, but incorporates a malicious dependency in the form of a malicious Go module hosted on GitHub (e.g., uniroute), causing the infection sequence to be triggered once the project is executed. This includes first determining the operating system of the victim's computer and delivering an appropriate next-stage payload (i.e., DownTroy) programmed in PowerShell (Windows), bash script (Linux), or AppleScript (macOS). Also deployed via DownTroy in the attacks targeting Windows are RooTroy, RealTimeTroy, a Go version of CosmicDoor, and Rust-based loader named Bof that's used to decode and launch an encrypted shellcode payload stored in the "C:\Windows\system32\" folder. "Our research indicates a sustained effort by the actor to develop malware targeting both Windows and macOS systems, orchestrated through a unified command-and-control infrastructure," Kaspersky said. "The use of generative AI has significantly accelerated this process, enabling more efficient malware development with reduced operational overhead." "The actor's targeting strategy has evolved beyond simple cryptocurrency and browser credential theft. Upon gaining access, they conduct comprehensive data acquisition across a range of assets, including infrastructure, collaboration tools, note-taking applications, development environments, and communication platforms (messengers)."
thehackernews.comOct 28, 2025extracted
North Korean Hackers Combine BeaverTail and OtterCookie into Advanced JS Malware
The North Korean threat actor linked to the Contagious Interview campaign has been observed merging some of the functionality of two of its malware programs, indicating that the hacking group is actively refining its toolset. That's according to new findings from Cisco Talos, which said recent campaigns undertaken by the hacking group have seen the functions of BeaverTail and OtterCookie coming closer to each other more than ever, even as the latter has been fitted with a new module for keylogging and taking screenshots. The activity is attributed to a threat cluster that's tracked by the cybersecurity community under the monikers CL-STA-0240, DeceptiveDevelopment, DEV#POPPER, Famous Chollima, Gwisin Gang, PurpleBravo, Tenacious Pungsan, UNC5342, Void Dokkaebi, and WaterPlum. The development comes as Google Threat Intelligence Group (GTIG) and Mandiant revealed the threat actor's use of a stealthy technique known as EtherHiding to fetch next-stage payloads from the BNB Smart Chain (BSC) or Ethereum blockchains, essentially turning decentralized infrastructure into a resilient command-and-control (C2) server. It represents the first documented case of a nation-state actor utilizing the method that has been otherwise adopted by cybercrime groups. Contagious Interview refers to an elaborate recruitment scam that began sometime around late 2022, with the North Korean threat actors impersonating hiring organizations to target job seekers and deceiving them into installing information-stealing malware as part of a supposed technical assessment or coding task, resulting in the theft of sensitive data and cryptocurrency. In recent months, the campaign has undergone several shifts, including leveraging ClickFix social engineering techniques for delivering malware strains such as GolangGhost, PylangGhost, TsunamiKit, Tropidoor, and AkdoorTea. Central to the attacks, however, are malware families known as BeaverTail, OtterCookie, and InvisibleFerret. BeaverTail and OtterCookie are separate but complementary malware tools, with the latter first spotted in real-world attacks in September 2024. Unlike BeaverTail, which functions as an information stealer and downloader, initial interactions of OtterCookie were designed to contact a remote server and fetch commands to be executed on the compromised host. The activity detected by Cisco Talos concerns an organization headquartered in Sri Lanka. It's assessed that the company was not intentionally targeted by the threat actors, but rather they had one of their systems infected, likely after a user fell victim to a fake job offer that instructed them to install a trojanized Node.js application called Chessfi hosted on Bitbucket as part of the interview process. Interestingly, the malicious software includes a dependency via a package called "node-nvm-ssh" published to the official npm repository on August 20, 2025, by a user named "trailer." The package attracted a total of 306 downloads, before it was taken down by the npm maintainers six days later. It's also worth noting that the npm package in question is one of the 338 malicious Node.js libraries flagged earlier this week by software supply chain security company Socket as connected to the Contagious Interview campaign. The package, once installed, triggers the malicious behavior by means of a postinstall hook in its package.json file that's configured to run a custom script called "skip" so as to launch a JavaScript payload ("index.js"), which, in turn, loads another JavaScript ("file15.js") responsible for executing the final-stage malware. Further analysis of the tool used in the attack has found that "it had characteristics of BeaverTail and of OtterCookie, blurring the distinction between the two," security researchers Vanja Svajcer and Michael Kelley said, adding it incorporated a new keylogging and screenshotting module that uses legitimate npm packages like "node-global-key-listener" and "screenshot-desktop" to capture keystrokes and take screenshots, respectively, and exfiltrate the information to the C2 server. At least one version of this new module comes equipped with an auxiliary clipboard monitoring feature to siphon clipboard content. The emergence of the new version of OtterCookie paints a picture of a tool that has evolved from basic data-gathering to a modular program for data theft and remote command execution. Also present in the malware, codenamed OtterCookie v5, are functions akin to BeaverTail to enumerate browser profiles and extensions, steal data from web browsers and cryptocurrency wallets, install AnyDesk for persistent remote access, as well as download a Python backdoor referred to as InvisibleFerret. Some of the other modules present in OtterCookie are listed below - Remote shell module, which sends system information and clipboard content to the C2 server and installs the "socket.io-client" npm package to connect to a specific port on the OtterCookie C2 server and receive further commands for execution File uploading module, which systematically enumerates all drives and traverses the file system in order to find files matching certain extensions and naming patterns (e.g., metamask, bitcoin, backup, and phrase) to be uploaded to the C2 server Cryptocurrency extensions stealer module, which extracts data from cryptocurrency wallet extensions installed on Google Chrome and Brave browsers (the list of extensions targeted partially overlaps with that of BeaverTail) Furthermore, Talos said it detected a Qt-based BeaverTail artifact and a malicious Visual Studio Code extension containing BeaverTail and OtterCookie code, raising the possibility that the group may be experimenting with new methods of malware delivery. "The extension could also be a result of experimentation from another actor, possibly even a researcher, who is not associated with Famous Chollima, as this stands out from their usual TTPs," the researchers noted. Contagious Interview Evolves with New OtterCandy Malware The disclosure comes as NTT Security Holdings shared details of a new malware called OtterCandy, deployed in connection with the Contagious Interview campaign since July 2025, targeting Windows, macOS, and Linux systems. An early sample of OtterCandy was uploaded to the VirusTotal platform in February 2025. OtterCandy, per the Japanese cybersecurity company, combines the features of OtterCookie and RATatouille, a remote access trojan (RAT) distributed via the supply chain compromise of the npm package "rand-user-agent" back in May 2025. This is the first time the attack has been attributed to North Korean threat actors. The obfuscated payload embedded within the npm package is designed to set up a stealthy communication channel with a remote server and exfiltrate files within a particular directory and execute shell commands, the latter of which is specific only to Windows, according to Aikido. The full list of supported commands is below - env, to search for secret filenames across the entire file system imp, to search for secret filenames within the home directory pat, to search for filenames matching a preset pattern within the current directory upload, to transmit system information, browser passwords, wallet files, and extension data (MetaMask, Phantom, and TronLink) from Google Chrome and Edge to the C2 server exec, to cancel in-progress scans or uploads (ss_stop), upload a single file (ss_upf), recursively upload the contents of a directory (ss_upd), change current directory (cd), or terminate the malware process (ss_del) OtterCandy is said to be distributed via a sub-cluster of activity tracked as ClickFake Interview (aka Cluster B), which involves deceiving users with ClickFix-style lures to run malicious commands so as to fix supposed camera or microphone issues when job seekers attempt to provide a video assessment on a fake website under their control. "OtterCandy is a RAT and Info Stealer implemented by Node.js," NTT Security said. "It is malware that combines elements of RATatouille and OtterCookie. OtterCandy accepts commands when connected to the C2 server via Socket.IO." The first-stage malware used to deliver OtterCandy is named DiggingBeaver, a JavaScript payload that's executed once the victim copies and runs the command via the Windows Run dialog. DiggingBeaver has also been found to distribute other known ClickFake Interview malware, such as GolangGhost and FROSTYFERRET. NTT Security said it also observed a new variant of OtterCandy (OtterCandy v2) in August 2025 that comes with expanded functionality to harvest data from three additional cryptocurrency wallet extensions (Suiet, Trust Wallet, and Rabby Wallet), as well as enhance the "ss_del" command to delete Windows Registry keys and erase files and directories. (The story was updated after publication on October 19, 2025, to include details of OtterCandy malware from NTT Security Holdings.)
thehackernews.comOct 17, 2025extracted
[Redirected] Memory Dump Issue in AWS CodeBuild
Memory Dump Issue in AWS CodeBuild Bulletin ID: AWS-2025-016 Scope: AWS Content Type: Important Release Date: 2025/07/25 6:00 PM PDT Description AWS CodeBuild is a fully managed on-demand continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. Security researchers reported a CodeBuild issue that could be leveraged for unapproved code modification absent sufficient repository controls and credential scoping. The researchers demonstrated how a threat actor could submit a Pull Request (PR) that, if executed through an automated CodeBuild build process, could extract the source code repository (e.g. GitHub, BitBucket, or GitLab) access token through a memory dump within the CodeBuild build environment. If the access token has write permissions, the threat actor could commit malicious code to the repository. This issue is present in all regions for CodeBuild. During our investigation, we identified this technique was leveraged by a threat actor who extracted the source code repository access token for the AWS Toolkit for Visual Studio Code and AWS SDK for .NET repositories. We have assigned CVE-2025-8217 for this, please refer to the AWS Security Bulletin AWS-2025-015 for additional information. Source code repository credentials are required in CodeBuild to access repository content, create webhooks for automated builds, and execute the build on your behalf. If a PR submitter obtains CodeBuild's repository credentials, they could gain elevated permissions beyond their normal access level. Depending on the permissions customers grant in CodeBuild, these credentials might allow elevated privileges like webhook creation, which CodeBuild requires to integrate with source code repositories and set up automated builds, or commit code to the repository. To determine if this issue was leveraged by an untrusted contributor, we recommend reviewing git logs, e.g. GitHub logs, and look for anomalous activity of the credentials granted to CodeBuild. We will update this bulletin if we have additional information to share. Resolution CodeBuild has included additional protections against memory dumps within container builds using unprivileged mode. However, because builds execute code committed by contributors in the build environment, they have access to anything the build environment has access to. Therefore, we strongly recommend customers do not use automatic PR builds from untrusted repository contributors. For public repositories that want to continue to support automatic builds of untrusted contributions, we advise using the self-hosted GitHub Actions runners feature in CodeBuild as it is not impacted by this issue. To disable automatic builds of PR from untrusted contributors, take any of the following approaches: Disable webhook builds by unchecking "Rebuild every time a code change is pushed to this repository" in the CodeBuild console, or Set a webhook event filter to not allow automatic builds from pull request events, or Set a webhook actor filter to allow pull requests builds from trusted users only If customers use the automatic build feature on PRs for untrusted contributors, and the credentials or access token provided to the CodeBuild environment have write permissions, we recommend rotating those credentials. In general, we recommend reviewing write permissions and revoking them unless absolutely necessary. References Acknowledgement We would like to thank the researchers from the Institute of Information Engineering, Chinese Academy of Sciences for collaborating on this issue through the coordinated vulnerability disclosure process. Please email [email protected] with any security questions or concerns.
aws.amazon.comAug 12, 2025extracted
14th July – Threat Intelligence Report
For the latest discoveries in cyber research for the week of 14th July, please download our Threat Intelligence Bulletin. TOP ATTACKS AND BREACHES McDonald’s has suffered a data breach that resulted in the exposure of chat transcripts, session tokens, and personal data from more than 64 million job applications submitted through its AI powered McHire chatbot platform. Data leaked included applicants’ names, email addresses, phone numbers, home addresses, availability, and personality test results, made accessible due to an insecure direct object reference (IDOR) vulnerability and admin accounts protected by weak default credentials. RocketGenius, the developer of WordPress plugin Gravity Forms, has experienced a cyber-attack that resulted in the compromise of plugin versions 2.9.11.1 and 2.9.12 available for manual download and composer install between July 10 and 11. The attack enabled remote code execution, extensive exfiltration of website metadata—including URLs, admin paths, installed themes, plugin and server versions—and the creation of a rogue admin account granting attackers complete control over affected websites, impacting potentially one million sites. Bitcoin Depot, a major Bitcoin ATM operator in the US, has suffered a data breach that resulted in the exposure of sensitive personal information belonging to nearly 27,000 customers, including full names, phone numbers, driver’s license numbers, addresses, dates of birth, and email addresses. Albemarle County in Virgina, United States, was hit by a ransomware attack that resulted in significant phone and technology outages, and the potential exposure of sensitive data belonging to local government and public-school employees, including driver’s license numbers, Social Security numbers, passport numbers, military IDs, and more. Some of the county’s 112,000 residents may have also had their names, addresses, and Social Security numbers compromised. GMX, a decentralized crypto exchange platform, has confirmed a cyber-attack that resulted in the theft of more than $40 million worth of cryptocurrency assets from its platform. The incident impacted user funds, with about $43 million in digital assets—including Ethereum, USDC, and DAI—being stolen and laundered by the hacker, affecting the platform’s more than 700,000 users. Nippon Steel Solutions, Japan’s largest steelmaker, has suffered a data breach after attackers exploited a zero-day vulnerability in its network equipment, resulting in unauthorized access to sensitive information. The breach has potentially exposed personal data of customers, partners, and employees. Ameos Group, a major Swiss hospital group, has experienced a cyber-attack that resulted in significant disruptions to its hospital operations across multiple locations. Critical IT systems were rendered inoperable, affecting both inpatient and outpatient care, as well as internal communication and documentation. VULNERABILITIES AND PATCHES Microsoft has published July’s Patch Tuesday, addressing 137 vulnerabilities across Microsoft products, including a publicly disclosed zero-day (CVE-2025-49719) in Microsoft SQL Server that allows remote, unauthenticated information disclosure due to improper input validation. Critical remote code execution vulnerabilities in Microsoft Office—triggered by malicious documents or preview pane viewing—and additional RCE flaws in Microsoft SharePoint (CVE-2025-49704) are also resolved. Details have been disclosed on a pre-authenticated SQL injection vulnerability (CVE-2025-25257, CVSS 9.8) in Fortinet FortiWeb, where exploitation can lead to remote code execution on unpatched systems. Attackers can inject arbitrary SQL via the Authorization header in HTTP requests, allowing unauthorized file creation and code execution through manipulated Python files. Exploits and technical details have been released publicly, greatly increasing the risk of compromise. Check Point IPS provides protection against this threat (Fortinet FortiWeb SQL Injection CVE-2025-25257) A technical analysis of the PerfektBlue vulnerability chain revealed four chained flaws (CVE-2024-45431 through CVE-2024-45434) in the Blue SDK Bluetooth stack used by OpenSynergy. The vulnerabilities enable remote code execution in over 350 million vehicles from Mercedes-Benz, Volkswagen, Skoda, and possibly Ford, and more than 1 billion embedded devices spanning automotive, industrial, consumer, mobile, and medical sectors. THREAT INTELLIGENCE REPORTS Check Point Research has released its June 2025 Malware Report highlighting AsyncRAT which was ranked number three among Top Malware. AsyncRAT was distributed via sophisticated multi-stage malware campaign exploiting expired Discord vanity invite links, leveraging trusted platforms such as GitHub, Bitbucket, and Discord for payload delivery and data exfiltration. The report also details additional malware families including FakeUpdates and Androxgh0st, affecting sectors such as education, healthcare, and government. Check Point Research has summarized key findings about the Scattered Spider threat group, which has recently targeted major airlines and diverse enterprises using sophisticated social engineering and phishing domain infrastructure. The group employs phishing sites that mimic corporate login portals (e.g., victimname-sso.com), MFA fatigue, vishing, SIM swapping, and uses both remote access tools and infostealers. Check Point has released findings revealing a 39% surge in weekly cyber-attacks targeting organizations in Latin America during the first half of 2025, averaging 2,716 weekly incidents compared to the global average of 1,955. Key threats include advanced malware such as RATs and botnets, while email was identified as the leading delivery vector.
research.checkpoint.comJul 14, 2025extracted