CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
‹Sat · 16 May 2026›
All daily briefs →
Daily brief · UTC day

Saturday, 16 May 2026

7 verified findings from 1 run · the settled record for this UTC day, in the classic brief order.

Criticality
Kind
Topic
Region
TL;DR · the day in one read
  1. 01node-ipc npm package backdoored, likely via an expired-domain maintainer takeover: three malicious versions steal developer and CI credentials on require(). node-ipc npm package (widely-used Node.js IPC library) hijacked, likely via an expired-domain account takeover; three malicious versions (9.1.6, 9.2.3, 12.0.1) exfiltrate cloud, CI/CD, SSH and Keychain credentials over DNS TXT (StepSecurity also reports an HTTPS channel that Socket did not find); rotate every secret on any workstation or CI runner that loaded one of the three versions (Socket Security, 2026-05-14 · StepSecurity, 2026-05-14). →
  2. 02SentinelOne: attackers turn build servers, CI/CD runners and developer workstations into the intrusion path. SentinelOne's post of 2026-05-15 describes CI/CD subversion seen in 2025: attackers on a vulnerable self-hosted TeamCity server ran a backdoor-deploying build job and stayed undetected for over a year, a stolen GitLab service-account token planted Ansible playbooks the pipeline ran automatically, Contagious Interview lured developers into running malware, and Sha1-Hulud registered rogue self-hosted GitHub runners. It recommends alerting on runner registrations, pipeline changes by service accounts and suspicious process behavior on build runners. →
  3. 03Unit 42: evolved Gremlin stealer hides its payload in .NET resources and hijacks live Chromium browser sessions. Unit 42 reported on 2026-05-15 a Gremlin stealer variant that moves its payload into an XOR-encoded .NET resource section, decrypts functions only when needed and, in one sample, sits under a commercial packer with instruction virtualization. New modules steal Discord tokens, swap copied cryptocurrency wallet addresses for the attacker's in real time and hijack live Chromium-based browser sessions over WebSocket; stolen data leaves as a ZIP uploaded to an attacker-controlled web panel, with the Telegram Bot API as an alternative channel. →

01Active threats, incidents & disclosures3 items

ROUTINEupdatedNATOA2

Suspected Dream Market main administrator "Speedstepper" arrested in Germany; US indictment traces reactivated marketplace wallets and gold purchases

On 2026-05-07, in a coordinated effort by German and US law enforcement, Owe Martin Andresen, 49, was arrested in Germany on German charges, and his residence and two other locations were searched (US DEA, 2026-05-13). A US federal grand jury had indicted him on 2026-01-13 on six counts of international concealment money laundering and six counts of concealment money laundering, each carrying up to 20 years, and Germany has charged him with several counts of concealment money laundering, each punishable by up to five years (US DEA, 2026-05-13). The DOJ indictment, unsealed in the week The Record reported it, accuses him of being the main administrator of Dream Market, a darknet marketplace launched in 2013 that announced its shutdown in 2019 (The Record, 2026-05-13); the release calls him the suspected main administrator, the role whose holder used the moniker "Speedstepper" and was not identified in the earlier prosecutions (US DEA, 2026-05-13). The case is investigated by the IRS-CI Cyber Crimes Unit and the DEA Miami Counternarcotic Cyber Investigations Task Force with substantial assistance from the Bundeskriminalamt Cybercrime Unit and the Zentrale Kriminalinspektion Oldenburg; the FBI, USPIS and HSI were part of the task force that investigated the marketplace between 2016 and 2022, whose prosecutions convicted the administrators "Oxymonster" and "KITT3N" in the US and the mid-level administrator "GOWRON" in the UK (US DEA, 2026-05-13).

Prosecutors allege that in November and December 2022 Andresen moved funds from the marketplace's dormant commission wallets into new consolidated wallets, activity that could only have been initiated by someone holding Dream Market's original private keys, and that in August 2023 he used an Atlanta-based cryptocurrency service provider to buy gold bars that were shipped to his home address in Germany; in total he is alleged to have laundered over $2 million between August 2023 and April 2025 (US DEA, 2026-05-13). The US Attorney says the commissions came from selling illegal drugs, stolen personally identifiable information, counterfeit identification documents and other items (US DEA, 2026-05-13). US agencies had kept watching the marketplace's wallets after the shutdown and found them untouched until then (The Record, 2026-05-13). The searches located about $1.7 million of gold bars and over $23,000 in cash, along with information identifying bank accounts and cryptocurrency wallets holding about $1.2 million believed to be Dream Market proceeds (US DEA, 2026-05-13).

On May 7, 2026, in a coordinated effort by both German and U.S. law enforcement, Andresen was arrested on German charges, and his residence and two other locations were searched.

Law enforcement also located information identifying several bank accounts and cryptocurrency wallets containing approximately $1.2 million of funds believed to be proceeds of the Dream Market.

US DEA 2026-05-13

An indictment unsealed this week by the DOJ accused Andresen of being the main administrator of Dream Market.

The Record 2026-05-13
Correctionrun 2026-10-21T1148Z-auditbodyclassificationentitiesevent_dateevidenceheadlinesourcessourcing_notesummarytitlesectorstechniquespriority

The arrest on 2026-05-07 was a coordinated German and US effort on German charges rather than a BKA arrest: the case is investigated by the IRS-CI Cyber Crimes Unit and DEA Miami with substantial assistance from the Bundeskriminalamt Cybercrime Unit and the Zentrale Kriminalinspektion Oldenburg, while the FBI, USPIS and HSI belonged to the task force that investigated the marketplace from 2016 to 2022 (US DEA, 2026-05-13). Only the US indictment accuses Andresen of being the main administrator; the German charges are concealment money laundering (US DEA, 2026-05-13; The Record, 2026-05-13). The 2022 transfers went into new consolidated wallets, not a single wallet, and the searches located about $1.7 million of gold bars and over $23,000 in cash and identified bank accounts and wallets holding about $1.2 million, rather than seizing $1.2 million in cryptocurrency (US DEA, 2026-05-13). The marketplace commissions behind the laundering came, the US Attorney says, from selling illegal drugs, stolen personally identifiable information, counterfeit identification documents and other items (US DEA, 2026-05-13).

threat16 May 05:00Zmulti-sourceOpen finding →
Sources: The Record · US DEA
HIGHupdatedNATOB1

node-ipc npm package backdoored, likely via an expired-domain account takeover: three malicious versions steal developer and CI credentials, flagged about three minutes after publication

On 2026-05-14, three malicious versions of the node-ipc npm package (9.1.6, 9.2.3 and 12.0.1) were published at the same time by a co-maintainer account with no prior publish history on the package (StepSecurity, 2026-05-14). The account's email domain had expired on 2025-01-10 and was re-registered on 2026-05-07, a week before the attack (The Hacker News, 2026-05-14). Socket assesses that the new domain owner could then trigger a standard npm password reset and gain publish rights without touching the maintainer's own infrastructure (Socket Security, 2026-05-14). CSO counts almost 700K weekly downloads and 424 dependent projects, while StepSecurity reports over 10 million weekly downloads (CSO Online, 2026-05-15 · StepSecurity, 2026-05-14). The 9.x releases are fabricated from the 12.x package structure, so projects on ^9, ~9.1.x, ~9.2.x, ^12 or ~12.0 ranges received a malicious build on their next install or lockfile refresh (StepSecurity, 2026-05-14). When StepSecurity published, npm's latest tag pointed to 12.0.1, so an unpinned npm install node-ipc pulled the compromised tarball (StepSecurity, 2026-05-14). As of 2026-10-21 the npm registry no longer lists 9.1.6, 9.2.3 or 12.0.1, and its latest tag points to 14.0.0 (npm registry, 2026-10-21).

The payload is an 80 KB obfuscated function appended to the CommonJS bundle node-ipc.cjs. It runs on every require('node-ipc') and uses no npm lifecycle hook, so tools that only scan preinstall and postinstall scripts miss it (StepSecurity, 2026-05-14). ESM-only consumers do not load the malicious file unless another dependency or a direct require loads node-ipc.cjs (Socket Security, 2026-05-14). The payload forks a detached child Node process that collects cloud provider credentials, SSH keys, Kubernetes tokens, GitHub CLI configuration, Terraform state, CI workflow files, .env files, shell history and macOS Keychain databases, gzips them and exfiltrates them (Socket Security, 2026-05-14 · StepSecurity, 2026-05-14). Four stacked obfuscation layers (string-array shuffling, control-flow flattening, dead-code injection and a custom reversed-nibble base-16 encoding) resist static analysis (StepSecurity, 2026-05-14). Socket found no persistence and no second-stage download, and its scanner flagged the publish within roughly three minutes (Socket Security, 2026-05-14).

Contradiction: the analyses disagree on payload details. StepSecurity and The Hacker News describe 90+ file-path patterns, an HTTPS POST channel alongside DNS TXT exfiltration, and a SHA-256 targeting gate that leaves 12.0.1 inert except on one targeted project (StepSecurity, 2026-05-14 · The Hacker News, 2026-05-14). Socket counts 113 macOS and 127 Linux patterns, says the payload uses DNS TXT queries and not HTTP, HTTPS or TLS for exfiltration, and finds the same malicious file in all three versions, with a hash gate that only changes what the module exports (Socket Security, 2026-05-14). Treat all three versions as active stealers.

Correctionrun 2026-09-30T0639Z-auditbodyclassificationtechniquesheadlinesummarytitle

As of 2026-09-30 no source said the malicious versions had been removed from the registry: when StepSecurity published, npm's latest tag pointed to the malicious 12.0.1 (StepSecurity, 2026-05-14). The payload fires on require() and uses no install hook, so disabling install scripts in CI does not stop it. Socket's advice is to review dependencies by their entrypoints and to rotate every secret on an affected host (Socket Security, 2026-05-14). Socket and StepSecurity disagree on the exfiltration channels, the pattern count and whether 12.0.1 is gated to one target (Socket Security, 2026-05-14 · StepSecurity, 2026-05-14), and all three versions should be treated as active. The entry previously named a domain registrar and Vue CLI and webpack tooling as dependents, which no cited source states.

Correctionrun 2026-10-11T1307Z-audittitleheadlinesummarysourcesbody

Socket calls the expired recovery-email domain the likely vector and frames the mechanism conditionally, assuming the maintainer's npm recovery address was hosted on that domain (Socket Security, 2026-05-14); StepSecurity instead says the maintainer credentials were either freshly compromised or the account was added as a maintainer specifically for this publish (StepSecurity, 2026-05-14). How the account was taken over is therefore not established.

Improvementrun 2026-10-21T0800Z-auditsourcesbody

As of 2026-10-21 the npm registry no longer lists 9.1.6, 9.2.3 or 12.0.1, and its latest tag points to 14.0.0 (npm registry, 2026-10-21), so a fresh unpinned install no longer resolves to a malicious version; the exposure now lies with hosts, build caches and local npm caches that already hold one of the three.

incident16 May 05:00Zmulti-sourceOpen finding →
NOTABLEupdatedNATOB2

GTIG: UNC6671 "BlackFile" vishing → AiTM → rogue-MFA → programmatic SharePoint exfiltration (1M+ files from one victim); DLS shutdown signals possible rebrand

Google Threat Intelligence Group published on 2026-05-15 an analysis of UNC6671, a financially motivated extortion cluster that adopted the "BlackFile" brand by February 2026 and has targeted dozens of organizations across North America, Australia and the UK (Google Threat Intelligence Group, 2026-05-15). Callers hired by the actor phone employees' personal mobile numbers, pose as internal IT or helpdesk staff citing a passkey migration or MFA update, and send the victim to a lookalike single sign-on portal on Tucows-registered domains, lately as organization-named subdomains with "passkey" or "enrollment" themes (Google Threat Intelligence Group, 2026-05-15). The operator relays the credentials and the MFA code or push approval to the real SSO provider in real time, then immediately registers a new attacker-controlled MFA device for persistence (Google Threat Intelligence Group, 2026-05-15). GTIG stresses that these compromises come from social engineering, not a vendor vulnerability (Google Threat Intelligence Group, 2026-05-15).

After access, the actor moves into connected SaaS applications (SharePoint, OneDrive, Zendesk, Salesforce), searches for strings such as "confidential" and "SSN", and exfiltrates with Python requests and PowerShell scripts through Microsoft Graph and direct HTTP GET requests against document URLs, reusing session cookies (for example FedAuth) captured during the vishing phase (Google Threat Intelligence Group, 2026-05-15). In one case the script downloaded more than a million files from SharePoint and OneDrive (Google Threat Intelligence Group, 2026-05-15). The direct-fetch method is often logged as FileAccessed rather than FileDownloaded, so it slips past SOCs that treat FileAccessed as benign (Google Threat Intelligence Group, 2026-05-15). In early intrusions the FileDownloaded records carried a spoofed Microsoft Office ClientAppId, which GTIG says served to bypass basic conditional access filters, while the user-agent showed python-requests or WindowsPowerShell (Google Threat Intelligence Group, 2026-05-15). In later intrusions the FileAccessed records named python-requests as the client application in AppAccessContext (Google Threat Intelligence Group, 2026-05-15). The sessions came from commercial VPN exit nodes and hosting providers (Google Threat Intelligence Group, 2026-05-15).

The BlackFile leak site went offline in late April 2026, came back on 2026-05-11 with a message that BlackFile "is shutting down… under this name", and was inaccessible at publication (Google Threat Intelligence Group, 2026-05-15). GTIG reads this as a possible transition phase rather than a permanent cessation, noting that extortion clusters commonly rebrand or disperse after shutdowns (Google Threat Intelligence Group, 2026-05-15). GTIG assesses UNC6671 as independent of ShinyHunters (UNC6240), although UNC6671 co-opted the ShinyHunters brand at least once (Google Threat Intelligence Group, 2026-05-15).

Triage: an Office client identity paired with a scripting-library user-agent is the mismatch GTIG found, and GTIG reads it as scripted access rather than a person using SharePoint (Google Threat Intelligence Group, 2026-05-15). A session source on a commercial VPN or hosting provider that is unusual for the user adds weight (Google Threat Intelligence Group, 2026-05-15).

Correctionrun 2026-09-30T0639Z-auditbodyclassificationtechniquestitleheadlinesummarypriorityentitiessectors

GTIG describes the leak-site shutdown as a possible transition phase rather than a permanent cessation, not as a probable rebrand (Google Threat Intelligence Group, 2026-05-15). The detection guidance is corrected to GTIG's own: the spoofed Microsoft Office ClientAppId appeared on FileDownloaded records, later FileAccessed records named python-requests as the client, and new MFA factor registrations are suspicious when immediately preceded by failed or abandoned MFA challenges (Google Threat Intelligence Group, 2026-05-15). The actor reused captured session cookies such as FedAuth, and GTIG does not describe theft of application access tokens (Google Threat Intelligence Group, 2026-05-15).

incident16 May 05:00Zsingle-sourceOpen finding →
NOTABLECVE-2026-44112 +3updatedNATOA2

OpenClaw "Claw Chain": four chainable sandbox, exec-allowlist and MCP loopback flaws (CVE-2026-44112, CVE-2026-44113, CVE-2026-44115, CVE-2026-44118) fixed in release 2026.4.22

Cyera disclosed four vulnerabilities in OpenClaw, an open-source platform for autonomous AI agents originally launched as Clawdbot in late 2025, on 2026-05-15 after reporting them to the maintainers in April (Cyera, 2026-05-15). OpenClaw's advisories of 2026-04-23 list the openclaw npm package up to release 2026.4.21 as affected and 2026.4.22 as fixed for all four (OpenClaw GHSA-wppj-c6mr-83jj, 2026-04-23; OpenClaw GHSA-5h3g-6xhh-rg6p, 2026-04-23; OpenClaw GHSA-x3h8-jrgh-p8jx, 2026-04-23; OpenClaw GHSA-r6xh-pqhr-v4xh, 2026-04-23). CVE-2026-44112 and CVE-2026-44113 are time-of-check/time-of-use races in the OpenShell sandbox's filesystem bridge, where a symlink swap redirects a write outside the intended mount root or makes a read return bytes from outside it (OpenClaw GHSA-wppj-c6mr-83jj, 2026-04-23; OpenClaw GHSA-5h3g-6xhh-rg6p, 2026-04-23). CVE-2026-44115 lets an allowlisted command hide shell expansion in an unquoted heredoc body, so the shell evaluates more than the approved command text shows, which Cyera says returns environment variables such as API keys and tokens (OpenClaw GHSA-x3h8-jrgh-p8jx, 2026-04-23; Cyera, 2026-05-15). CVE-2026-44118 sits on the loopback MCP path, which accepted spoofable owner-context metadata from request headers and so let a non-owner loopback client act as owner for owner-gated operations such as gateway configuration, cron scheduling and execution-environment management (OpenClaw GHSA-r6xh-pqhr-v4xh, 2026-04-23; Cyera, 2026-05-15).

Cyera's chain starts from code execution inside the OpenShell sandbox through a malicious plugin, prompt injection or compromised external input, uses the read escape and the heredoc flaw to expose credentials, secrets and files, the loopback flaw for owner-level control of the agent runtime, and the write escape to plant backdoors or change configuration; it says each step looks like normal agent behavior to traditional controls (Cyera, 2026-05-15). Cyera rates CVE-2026-44112 at CVSS 9.6 and CVE-2026-44115 at 8.8 (Cyera, 2026-05-15), VulnCheck scores them 8.4 and 8.7 in CVSS 4.0 (VulnCheck, CVE-2026-44112; VulnCheck, CVE-2026-44115), and OpenClaw's own advisory for the heredoc allowlist bypass rates it moderate (OpenClaw GHSA-x3h8-jrgh-p8jx, 2026-04-23). Cyera counts about 65,000 (Shodan) and about 180,000 (Zoomeye) publicly accessible OpenClaw instances as of May 2026 (Cyera, 2026-05-15). Neither Cyera nor the vendor advisories report exploitation.

A time-of-check/time-of-use race around OpenShell sandbox filesystem writes could let a symlink swap redirect a write outside the intended local mount root.

An allowlisted command containing an unquoted heredoc could hide shell expansion in the heredoc body.

The loopback MCP path accepted spoofable owner-context metadata from request headers, which could allow a non-owner loopback client to present itself as owner for owner-gated operations.

OpenClaw

A malicious plugin, prompt injection, or compromised external input gains code execution inside the OpenShell sandbox.

Assume any environment variable or credential reachable by OpenClaw processes may be compromised.

Cyera Research 2026-05-15
Correctionrun 2026-10-21T1148Z-auditactionsaffected_productsbodyclassificationcvesevidenceheadlineprioritysourcessourcing_notesummarytechniquestitle

CVE-2026-44115 does not hide expansion tokens in environment-variable names: an allowlisted command containing an unquoted heredoc can hide shell expansion in the heredoc body, so the shell runs more than the approved text shows (OpenClaw GHSA-x3h8-jrgh-p8jx, 2026-04-23). Cyera reports about 65,000 instances on Shodan and about 180,000 on Zoomeye as two separate counts, not a combined 245,000, and its chain runs from a foothold inside the sandbox through the read escape and the heredoc flaw (credentials and files), then the loopback flaw (owner control), to the write escape (backdoors and persistence) (Cyera, 2026-05-15). The advisories list release 2026.4.21 and earlier as affected and 2026.4.22 as the fix for all four (OpenClaw GHSA-r6xh-pqhr-v4xh, 2026-04-23). The 9.6 for CVE-2026-44112 is Cyera's score; VulnCheck scores it 8.4 in CVSS 4.0 (VulnCheck, CVE-2026-44112), and OpenClaw's advisory for the heredoc bypass rates it moderate (OpenClaw GHSA-x3h8-jrgh-p8jx, 2026-04-23).

vulnerability16 May 05:00Zmulti-sourceOpen finding →
ROUTINECVE-2025-54518updatedNATOA2

AMD-SB-7052 / CVE-2025-54518: AMD Zen 2 op-cache corruption lets local code run instructions at a higher privilege, guest to host included (CVSS 7.3); OS updates on EPYC 7002, OEM BIOS updates on Ryzen

AMD disclosed on 2026-05-12 that improper isolation of shared resources in the CPU operation cache of Zen 2-based products can cause incorrect instructions to execute at a higher privilege level; it scores CVE-2025-54518 at 7.3 on CVSS 4.0, with local access, high attack complexity and low privileges, and found it internally (AMD Product Security, 2026-05-12). Xen says code of any privilege could escalate, including userspace to kernel and guest to host, that only AMD Fam17h (Zen 2) CPUs are believed vulnerable, that all Xen versions are affected and that there is no mitigation other than its patches (Xen Project, 2026-05-12). Microsoft lists the flaw as not exploited or publicly disclosed and rates it Exploitation Unlikely, and says the latest Windows builds enable the mitigation (MSRC, CVE-2025-54518).

The fix depends on the product line: for EPYC 7002 and EPYC Embedded 7002 processors AMD's mitigation is an OS update from the OS vendor, while for Ryzen 3000, 4000, 5000, 7020 and 7030 series, Threadripper PRO 3000 WX and Ryzen Embedded V2000 AMD released Platform Initialization firmware to OEMs between October and December 2025, to be installed as an OEM BIOS update, for example ComboAM4v2 PI version 1.2.0.10 for Ryzen 3000, 4000 and 5000 desktop parts (AMD Product Security, 2026-05-12). NCSC-NL lists updates from Debian (Xen), Dell PowerEdge, Fedora, Google Cloud Platform, Lenovo and Microsoft Windows (NCSC-NL, 2026-05-15).

AMD has identified a vulnerability in the CPU operation (op/µop) cache on Zen 2‑based products that can cause incorrect instructions to be executed at a higher privilege level.

AMD recommends updating to the Platform Initialization (PI) version indicated below.

AMD Product Security 2026-05-12

Code of any privilege could escalate to a higher privilege, including userspace to kernel, and guest to host.

Xen Project

This CVE is being documented in the Security Update Guide to announce that the latest builds of Windows enable the mitigation and provide protection against the vulnerability.

Microsoft Security Response Center 2026-05-12
Correctionrun 2026-10-21T1148Z-auditactionsaffected_productsbodyclassificationcvesevent_dateevidenceheadlinesourcessourcing_notesummarytechniquestitlepriority

The mitigation does not ship as microcode in a Windows update for every affected chip: AMD lists an OS update only for EPYC 7002 and EPYC Embedded 7002 processors, and for Ryzen 3000 to 7030 series, Threadripper PRO 3000 WX and Ryzen Embedded V2000 it recommends the Platform Initialization versions in its table, delivered as OEM BIOS updates (AMD Product Security, 2026-05-12). Microsoft says the latest Windows builds enable the mitigation, not that they carry it for all processors (MSRC, CVE-2025-54518), so a Windows build check cannot confirm a Ryzen host is protected, and a processor-ID query reports the CPU model rather than whether the mitigation is in place.

NCSC-NL lists Fedora and Lenovo among the vendors with updates (NCSC-NL, 2026-05-15).

vulnerability16 May 05:00Zmulti-sourceOpen finding →

03Research, reports & policy2 items

NOTABLECVE-2023-42793exploitedupdatedNATOB2

SentinelOne "Living Off the Pipeline": attackers subverted TeamCity, GitLab automation, self-hosted runners and developer workstations in 2025

SentinelOne's post of 2026-05-15 describes how attackers in 2025 went after the infrastructure that builds and ships software, not only its dependencies (SentinelOne, 2026-05-15). In one case attackers exploited a vulnerable self-hosted TeamCity server (the post links JetBrains' advisory for CVE-2023-42793), created a benign-looking build configuration that a trusted build agent ran with SYSTEM privileges, deployed a backdoor into internal environments and stayed undetected for more than a year (SentinelOne, 2026-05-15). JetBrains fixed CVE-2023-42793, an unauthenticated remote-code-execution flaw, in TeamCity On-Premises 2023.05.4 (JetBrains, 2023-09-21) and warned that backdoors planted before the patch persist after it (JetBrains, 2023-10-18). In an intrusion from SentinelOne's annual threat report, a compromised GitLab service-account token was used to create projects with malicious Ansible playbooks that the organization's pipeline then executed automatically (SentinelOne, 2026-05-15).

The post's other examples target people and runners: Contagious Interview sent developers in cryptocurrency and blockchain fraudulent job offers leading to fake skill-assessment sites, where a fabricated error told them to run commands that silently installed malware with access to their SSH keys, tokens and credentials, and the Sha1-Hulud campaign registered infected systems as self-hosted GitHub runners under attacker-defined names and used workflows that ran code when someone commented in a repository discussion (SentinelOne, 2026-05-15). Malicious versions of popular build packages ran reconnaissance scripts during installation that harvested tokens and inspected environments, and phished maintainer accounts appended malicious code to legitimate package updates (SentinelOne, 2026-05-15).

Triage: compiling, downloading packages, invoking scripts and opening connections are normal build activity, so a malicious job under a valid service account on a trusted runner looks legitimate unless the account acts outside its role; SentinelOne's discriminators are who created the job, what changed, where the runner was registered and which secrets were accessed (SentinelOne, 2026-05-15).

After gaining access, they created a benign-looking build configuration that was executed by a trusted build agent running with SYSTEM privileges.

The attacker used the token to create projects containing malicious Ansible playbooks, which were then automatically executed by the organization’s CI/CD pipeline.

Build runners should be treated as high-value systems, monitored for suspicious child processes, credential access attempts, reverse tunnels, and persistence mechanisms.

If a malicious job executes under a valid service account on a trusted runner, the behavior may appear legitimate unless the account performs actions that clearly deviate from its role.

SentinelOne 2026-05-15

The vulnerability may enable an unauthenticated attacker with HTTP(S) access to a TeamCity server to perform a remote code execution (RCE) attack and gain administrative control of the TeamCity server.

JetBrains 2023-09-21
Correctionrun 2026-10-21T1148Z-auditaffected_productsbodyclassificationconfidencecvesevidenceheadlinesectorssourcessourcing_notesummarytechniquestitle

The monitoring priorities SentinelOne gives are new runner registrations and unusual runner names, new or modified pipelines created by service accounts, jobs interacting with unfamiliar repositories, workflows that establish network tunnels, and suspicious child processes, credential access attempts, reverse tunnels and persistence on build runners (SentinelOne, 2026-05-15); the post names no audit-event type, source-address criterion or specific binaries. It walks through examples rather than a three-case taxonomy, and the rogue self-hosted runners and discussion-comment workflow triggers belong to the Sha1-Hulud campaign (SentinelOne, 2026-05-15). The TeamCity case links CVE-2023-42793, an unauthenticated remote-code-execution flaw fixed in TeamCity On-Premises 2023.05.4 (JetBrains, 2023-09-21); JetBrains warns that backdoors planted before patching are likely to persist after it, so a server patched after early October 2023 needs a compromise assessment (JetBrains, 2023-10-18).

research16 May 05:00Zsingle-sourceOpen finding →
NOTABLEupdatedNATOB2

Unit 42: Gremlin stealer hides its payload in XOR-encoded .NET resources and adds a crypto clipper, Discord token theft and WebSocket session hijacking

Unit 42 identified a new Gremlin stealer variant that bundles stolen browser cookies, session tokens, clipboard contents, cryptocurrency wallet data and FTP and VPN credentials into a ZIP archive named with the victim's public IP address and uploads it to an attacker-controlled site, while exfiltration through private web panels or the Telegram Bot API stays as in earlier builds (Unit 42, 2026-05-15). The variant moves its payload into the .NET resource section masked with single-byte XOR encoding, decrypts and maps each critical function into memory only when needed, and hides its strings behind a runtime decoder that reads them from an embedded encrypted resource; one sample is wrapped in a commercial packer that turns the code into custom bytecode run by a private virtual machine (Unit 42, 2026-05-15). New modules extract Discord tokens by scanning multiple paths with regex validation, watch the clipboard for wallet-address patterns and replace the victim's address with the attacker's in real time, and hijack live sessions in Chromium-based browsers over WebSocket by requesting the data directly from the running browser process, which bypasses modern cookie protections (Unit 42, 2026-05-15). The post does not describe how Gremlin is delivered.

In this version, the malware authors have shifted the malicious payload into the .NET Resource section, masking it with XOR encoding to bypass signature-based detection and heuristic scanning.

When it detects a match, the malware replaces the victim's address with the attacker’s wallet in real time, diverting funds during transactions.

This allows Gremlin stealer to hijack active, live browser sessions and bypass modern cookie protections by requesting the data directly from the running browser process.

The malware names the file using the victim’s public IP address to identify the source, and then uploads it to the attacker-controlled site, as shown in Figure 3.

Unit 42
Correctionrun 2026-10-21T1148Z-auditaffected_productsbodyclassificationevidenceheadlinesourcessourcing_notesummarytechniquestitle

The analyzed variant bundles its haul into a ZIP archive named with the victim's public IP address and uploads it to an attacker-controlled site, with private web panels or the Telegram Bot API as the exfiltration methods carried over from earlier builds; Unit 42 does not describe an HTTPS POST with Telegram as a secondary channel (Unit 42, 2026-05-15). The clipper replaces any copied address matching its cryptocurrency wallet patterns, not only Bitcoin and Ethereum addresses, and saved passwords are not among the data Unit 42 lists (Unit 42, 2026-05-15). The session-hijack module works by requesting the data directly from the running Chromium-based browser process over WebSocket, and one sample is protected by a commercial packer that runs the code as custom bytecode on a private virtual machine (Unit 42, 2026-05-15).

research16 May 05:00Zsingle-sourceOpen finding →
Verification & coverage notes1 run

2026-05-16-5bc123a0 · Claude Opus 4.7 · window 36 h · 10 entries published

  • Items dropped (duplicate of prior coverage):
    • Exim CVE-2026-45185 ("Dead.Letter" pre-auth heap UAF via BDAT/GnuTLS), already covered as a § 2 Trending Vulnerability in briefs/2026-05-13.md (primary source XBOW research blog 2026-05-12). S1's re-surfacing in this run includes the discoverer attribution (Federico Kirschbaum / XBOW) and patch detail (4.99.3 fixes by resetting input-processing stack on TLS close_notify during BDAT), none of which constitute material new development under PD-8. No § 4 UPDATE warranted.
  • Items dropped / deferred (out-of-window recency, PD-7):
    • Microsoft IR case study "Undermining the trust boundary, 106-day stealth intrusion via trusted HPE Operations Manager (HPOM)" (Microsoft IR, 2026-05-12): primary source published 2026-05-12, more than 36 h before this run's start; no fresher in-window development. Substantive technical research with strong defender takeaways (HPOM VBScript push as living-off-trusted-tools persistence, Updater.dll network-provider DLL credential interception, 106-day undetected dwell), deferred to the weekly summary for cross-day consolidation. out-of-window: primary source 2026-05-12, window_hours=36.
    • Cushman & Wakefield vishing breach (ShinyHunters Salesforce CRM data + Qilin separate listing): initial disclosure 2026-05-05, victim statement 2026-05-05, HIBP indexing 2026-05-12. All evidence dates fall outside the 36-hour window. Pattern (vishing → SaaS-CRM credential capture → bulk record exfil) is consistent with previously-covered ShinyHunters operations and adds no fresh TTP. out-of-window: primary sources 2026-05-05 to 2026-05-12, window_hours=36.
  • F5 BIG-IP / BIG-IQ May 2026 Quarterly Security Notification (K000160932): NCSC-NL flagged the bundle as HIGH on 2026-05-15 (NCSC-NL NCSC-2026-0162, 2026-05-15). Per-CVE enumeration requires authenticated myF5 portal access and could not be obtained from the public CSAF excerpt in this run. Operators of F5 BIG-IP / BIG-IQ in Swiss financial-sector, telco, and large public-sector perimeters should pull the K-article matrix directly; we will surface the per-CVE detail in the next brief that pivots through an authenticated review or a corroborating researcher write-up.
  • Sub-agent telemetry: S1 returned (Claude Sonnet 4.6, 236 s, 7 webfetch + 6 websearch + 18 bridge). S2 returned (Claude Sonnet 4.6, 245 s, 14 webfetch + 8 websearch + 12 bridge). S3 returned (Claude Sonnet 4.6, 616 s, 12 webfetch + 0 websearch + 8 bridge). S4 returned (Claude Sonnet 4.6, 524 s, 12 webfetch + 12 websearch + 11 bridge).
  • Item-overlap consolidation: CVE-2026-42897 Exchange OWA XSS was independently surfaced by S1, S2, S3, and S4, consolidated into one § 2 item, one § 5 deep dive, and the § 0 Immediate Action callout, with sources pooled across all four sub-agent returns. Kazuar / Secret Blizzard was surfaced by S2 and S3, consolidated into one § 1 item. node-ipc npm was surfaced by S3 and S4, consolidated into one § 1 item.
  • Single-source items: Gremlin Stealer evolved (Palo Alto Networks Unit 42, 2026-05-15), sole reputable primary, no independent corroboration found in window. SentinelOne "Living Off the Pipeline" CI/CD subversion taxonomy (SentinelOne, 2026-05-15), sole primary; the analytical content draws on prior public CVE-2023-42793 / Contagious Interview reporting, but the synthesis is single-sourced.
  • Coverage gaps / fetch failures:
    • databreaches-net: WebFetch returned 403 (5th consecutive run failing); WebSearch fallback used for breach-story discovery, no unique stories lost in this run. Rotation-priority signal preserved for the next run.
    • inside-it-ch: Cloudflare Managed Challenge blocked WebFetch (4th consecutive run); WebSearch fallback found no CH-specific items beyond what NCSC-CH posts surfaced. Rotation-priority signal preserved.
    • bleepingcomputer: rotation-priority source, multiple article URLs returned 403; URLs successfully fetched by S2 (e.g. the Microsoft Exchange zero-day article) used after cross-confirmation; broader feed listing not enumerated.
    • helpnetsecurity: rotation-priority source, known 429 rate-limit; one article cited (CVE-2026-42897 coverage) fetched successfully and corroborated.
    • cert-eu: no new advisories in the 36-hour window (latest 2026-006 dated 2026-05-06).
    • anssi-fr (CERT-FR): most recent avis bulletins outside the 36-hour window (latest 2026-05-12 / 13).
    • sophos-xops: feed returned HTTP 503; no items retrieved this run.
    • sekoia: no new posts in window (latest 2026-04-23).
    • cert-pl: SPA listing not navigated this run.
    • cnil-fr: site under scheduled maintenance 2026-05-13 to 2026-05-18 per maintenance notice.
    • sec-disclosures-edgar: SEC EDGAR Item 1.05 bridge returned 0 cyber-disclosure filings for the 2026-05-12 to 2026-05-16 window, quiet period for material cyber disclosures.
  • Coverage gaps: databreaches-net (403 5×); inside-it-ch (Cloudflare 4×); cert-eu (no in-window advisories); anssi-fr (no in-window AVI); sophos-xops (feed 503); sekoia (no in-window posts); cert-pl (SPA listing not navigated); cnil-fr (scheduled maintenance); sec-disclosures-edgar (no in-window 8-K Item 1.05 filings).
  • Verification status: CLEAN at iteration 4 (4 iterations, model-rotated). Iter 1 (Opus): 4 truth findings (Period 2 ESU citation, BlackFile ClientAppId location, Gremlin SetClipboardViewer API, node-ipc 822K download count), all fixed. Iter 2 (Sonnet): 2 truth + 1 editorial + 2 advisory (AMD-SB-7052 CVE/CVSS missing → CVE-2025-54518 CVSS 7.3 added, node-ipc DNS TXT count unsupported → dropped, Gremlin detection SetClipboardViewer still unsupported → softened, Fedora/Lenovo advisory IDs unverified → IDs dropped, helpdesk-priviledged typo), all fixed. Iter 3 (Opus, cold): 4 truth + 1 advisory (Gremlin Brave browser, OpenClaw "2026.4.22" version label, Kazuar "European" narrowing, SentinelOne Sha1-Hulud pattern claim, Aqua Blizzard paraphrase strength), all fixed. Iter 4 (Sonnet, with deltas): CLEAN, all iter-3 remediations verified correct against re-fetched primary sources. verification_residual_count: 0.

Unmatched action items (migrated)

  • Inventory every node-ipc install across developer workstations and CI/CD runners (transitive deps included); rotate every credential accessible from any environment that installed 9.1.6 / 9.2.3 / 12.0.1. Run npm ls node-ipc against every project; flag any install whose timestamp falls between 2026-05-14 publish-time and registry removal. Treat any match as a full developer-secret compromise: cloud SDK profiles, SSH keys, Kubernetes contexts, GitHub / npm / Git tokens, Terraform state, .env files, and macOS Keychain databases were all in scope. Going forward, enforce npm ci --ignore-scripts and lockfile-based installs in CI, monitor outbound DNS to the bt.node.js suffix, and add domain-expiry monitoring for maintainer email domains of critical dependencies. See § 1 (node-ipc entry).
  • Add the BlackFile vishing → AiTM → rogue-MFA → SharePoint-API exfiltration detections to M365 / Okta monitoring. Concretely: alert on Okta system.multifactor.factor.setup events without a preceding user-initiated session; alert on M365 audit FileAccessed events with AppAccessContext.ClientAppId == d3590ed6-52b3-4102-aeff-aad2292ab01c AND user-agent containing python-requests or PowerShell; require Conditional Access compliant-device for Graph API access by administrative accounts; move helpdesk-privileged accounts to FIDO2 phishing-resistant MFA so the live-vishing capture-and-replay chain fails at the second factor. See § 1 (BlackFile entry).
  • Hunt for Kazuar P2P artefacts on systems hosting European government, diplomatic, or defence workloads. Concretely: Sysmon EID 17 / 18 for Mailslot creation from non-standard processes; registry audit on HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages for unsigned DLL additions; flag programmatic Exchange Web Services authentication originating from non-Exchange processes against the organisation's own mail servers. Where Aqua Blizzard / Gamaredon presence has been previously detected, treat Kazuar implant presence as a concurrent hypothesis. See § 1 (Secret Blizzard entry).

Migrated from briefs/2026-05-16.md (v2).