The Hot Drop for 11-12-2026

What to do today

  • Act Immediately upgrade MongoDB Server to version 9.0.7, 8.3.16, or 8.0.37 to remediate the critical use-after-free vulnerability.
  • Act Immediately update Microsoft 365 Apps for Enterprise to the specified version to prevent credential theft from the spoofing flaw.
  • Act Immediately update Google Chrome to version 157.0.8103.50 on all platforms to address the actively exploited use-after-free vulnerability.
  • Act Security operations teams should search commits made since November 10 for specific messages such as 'ci: refresh build cache' and 'chore: add dependency audit workflow' to identify malicious changes.
  • Act Immediately audit AWS environments for unauthorized use of valid IAM users and assumed EC2 roles to revoke compromised credentials.
  • Act Immediately update Microsoft .NET 10.0 installed on Linux to version 10.0.15 to mitigate the elevation of privilege vulnerability.

Today's bottom lines

#StorySeverityStatusBottom line
1CVE-2026-118383: MongoDB Server arbitrary code executionCVSS 9.5New in threadMongoDB Server contains a critical use-after-free vulnerability, tracked as CVE-2026-118383, that allows an unauthenticated attacker to crash the server or possibly execute arbitrary code. Organizations running replica set members, including shards and config servers, are at risk, while standalone instances are unaffected. Teams should immediately upgrade to MongoDB Server versions 9.0.7, 8.3.16, or 8.0.37 and audit security groups to block inbound internet access to the database.
2CVE-2026-124194: Microsoft 365 Apps for EnterpriseCVSS 6.5 · KEVNewMicrosoft patched an actively exploited spoofing vulnerability in Outlook that allows attackers to steal Windows authentication information through a malicious message file. Organizations using Microsoft 365 Apps for Enterprise, Office LTSC 2021, or Office LTSC 2024 should apply the available updates immediately to prevent credential theft. Federal agencies must complete remediation by November 24, 2026, to comply with the CISA Known Exploited Vulnerabilities catalog deadline.
3CVE-2026-125350: Google Chrome use after freeCVSS 8.8 · KEVNewCISA added a Google Chrome use-after-free vulnerability to its Known Exploited Vulnerabilities catalog on November 10, 2026, stating that attackers are already using the flaw. Google shipped the patch for the vulnerability on November 9, 2026.
4Hackers Compromise Nearly 5,000 GitHub Accounts to Steal Secrets From Software Development Pipelines—New in threadSince November 10, 2026, a threat actor has used stolen GitHub credentials to push a credential-stealing payload into tens of thousands of repositories, targeting software development secrets and cloud access. Organizations should immediately search commits made since November 10 for specific messages such as 'ci: refresh build cache' and 'chore: add dependency audit workflow' to identify and remove the malicious changes. Security teams must also review AWS CloudTrail for unauthorized access events and remove any IAM user access keys created since November 10 to prevent the attacker from maintaining long-lived backdoors in cloud accounts.
5Hackers use AntiFox AI agents in AWS credential-theft attacks—NewAttackers are using AntiFox, an open-source AI penetration-testing platform, to compromise web applications and steal Amazon Web Services credentials. Organizations with internet-facing web services and AWS environments should care because the activity involves confirmed malicious actions against these assets, including the use of valid AWS identities to access production secrets. Security teams should immediately audit AWS environments for unauthorized use of IAM users and assumed EC2 roles and review logs for ASPX web shell activity on internet-exposed Microsoft Internet Information Services servers.
6CVE-2026-114146: Microsoft .NET 10.0 installed on LinuxCVSS 9NewMicrosoft released a security advisory on 2026-11-10 for a new elevation of privilege vulnerability in ASP.NET Core, identified as CVE-2026-114146. The flaw allows an authorized attacker to elevate privileges over a network due to incorrect authorization in the framework. IT teams should immediately update Microsoft .NET 10.0 on Linux to version 10.0.15 to mitigate the risk.

Story 1 of 6

CVE-2026-118383: MongoDB Server arbitrary code execution

  • New in thread
  • CVE-2026-118383
  • CVSS 9.5
  • Not in KEV

Bottom line

MongoDB Server contains a critical use-after-free vulnerability, tracked as CVE-2026-118383, that allows an unauthenticated attacker to crash the server or possibly execute arbitrary code. Organizations running replica set members, including shards and config servers, are at risk, while standalone instances are unaffected. Teams should immediately upgrade to MongoDB Server versions 9.0.7, 8.3.16, or 8.0.37 and audit security groups to block inbound internet access to the database.

StoryCVE-2026-118383: MongoDB Server arbitrary code execution
AffectedMongoDB MongoDB Server
SeverityCVSS 9.5 (v4.0)
CISA KEVNot listed
Exploitation1 reported point on attack activity (see What happened)
CoverageNew development in an ongoing thread
Outlets reporting3
New since last covered14 of 14 facts
What happened — MongoDB announced on 2026-11-10 that it discovered a critical vulnerability in its server software internally and was not aware of any expl…

MongoDB announced on 2026-11-10 that it discovered a critical vulnerability in its server software internally and was not aware of any exploitation attempts at the time of the announcement. The flaw, tracked as CVE-2026-118383, is a use-after-free vulnerability in the replication component of MongoDB Server. MongoDB rated the vulnerability 9.5 out of 10 on the CVSS 4.0 severity scale. The vulnerability affects replica set members, including those used by shards and config servers, but standalone mongod instances are unaffected.

An unauthenticated attacker can trigger the issue by sending two requests, as vulnerable servers accept ping before login. Turning on authentication does not prevent this attack. The vulnerability occurs when a newly elected primary completes catch-up, causing the server to use memory it has already freed. MongoDB says the flaw may also result in arbitrary code execution in the server process under certain conditions.

Who is affected — MongoDB Server replica set members, including those used by shards and config servers, are affected by the vulnerability.

MongoDB Server replica set members, including those used by shards and config servers, are affected by the vulnerability. Standalone mongod instances are not affected. The flaw is a critical use-after-free vulnerability in MongoDB Server's primary catch-up process. The vulnerability carries a CVSS v4.0 score of 9.5.

What to do — IT and patching teams should upgrade MongoDB Server to version 9.0.7, 8.3.16, or 8.0.37 immediately to remediate the vulnerability.

Now

  • IT and patching: IT and patching teams should upgrade MongoDB Server to version 9.0.7, 8.3.16, or 8.0.37 immediately to remediate the vulnerability.
  • Security operations: Security operations teams should review Datadog Cloud Security Management findings for affected hosts and container images to identify vulnerable instances.

Next

  • Security operations: Security operations teams should audit security groups to ensure they do not allow inbound MongoDB access from the internet.
How solid this is, and what is missing — Three distinct outlets are reporting on the vulnerability, including Datadog Security Labs, The Hacker News, and the GitHub Advisory Databa…

Three distinct outlets are reporting on the vulnerability, including Datadog Security Labs, The Hacker News, and the GitHub Advisory Database. The Hacker News reported that MongoDB released fixed versions of the database earlier this week. The CVE record lists MongoDB Server versions before 9.0.7, 8.3.16, and 8.0.37 as affected, with the respective fixed versions carrying the patch. No confirmed disagreements between outlets were identified.

No timeline updates were identified.

ATT&CK techniques observed — No ATT&CK techniques were identified in current sources.

No ATT&CK techniques were identified in current sources.

Indicators of compromise — 5 defanged indicators
TypeIndicatorRoleOutlet
ipv6[:][:]caunknowngithub.com
ipv6d[:][:]unknowngithub.com
ipv6e[:][:]unknowngithub.com
sha123dfc542199ab3b88d6a9420b6cd3f125a897620unknowngithub.com
sha16111165c32bfc74f197e2dfeb9480d0b52154d68unknowngithub.com
Detection and hunting — Datadog Cloud Security Management reports findings for CVE-2026-118383.

Datadog Cloud Security Management reports findings for CVE-2026-118383. Analysts should check the vulnerability findings for affected hosts and container images. Datadog Cloud Security Management also flags security groups that allow inbound MongoDB access from the internet.

Timeline and references — 5 dated entries
DateEventSource
2026-11-10MongoDB announced a security update on November 10 stating it found the vulnerability internally and was not aware of exploitation attempts at the time.securitylabs.datadoghq.com
2026-11-11MongoDB released fixed versions of the database earlier this week.thehackernews.com
Reported 2026-11-11The vulnerability affects replica set members, including those used by shards and config servers, but standalone mongod instances are unaffected.securitylabs.datadoghq.com
Reported 2026-11-11CVE-2026-118383 is a critical use-after-free vulnerability in MongoDB Server's primary catch-up process with a CVSS v4.0 score of 9.5.securitylabs.datadoghq.com
Reported 2026-11-11An unauthenticated client can set up the crash with two ping requests because vulnerable servers accept ping before login, and turning on authentication does not prevent this.securitylabs.datadoghq.com

Back to top

Story 2 of 6

CVE-2026-124194: Microsoft 365 Apps for Enterprise

  • New
  • CVE-2026-124194
  • CVSS 6.5
  • In CISA KEV

Bottom line

Microsoft patched an actively exploited spoofing vulnerability in Outlook that allows attackers to steal Windows authentication information through a malicious message file. Organizations using Microsoft 365 Apps for Enterprise, Office LTSC 2021, or Office LTSC 2024 should apply the available updates immediately to prevent credential theft. Federal agencies must complete remediation by November 24, 2026, to comply with the CISA Known Exploited Vulnerabilities catalog deadline.

StoryCVE-2026-124194: Microsoft 365 Apps for Enterprise
AffectedMicrosoft Microsoft 365 Apps for Enterprise Microsoft Office LTSC 2021 Microsoft Office LTSC 2024
SeverityCVSS 6.5 (v3.1)
CISA KEVListed, added 2026-11-10
Exploitation1 reported point on attack activity (see What happened)
CoverageNew story
Outlets reporting2
New since last covered28 of 28 facts
What happened — CISA added CVE-2026-124194, an actively exploited Microsoft Outlook spoofing vulnerability, to its Known Exploited Vulnerabilities catalog…

CISA added CVE-2026-124194, an actively exploited Microsoft Outlook spoofing vulnerability, to its Known Exploited Vulnerabilities catalog on November 10, 2026. The agency established a November 24, 2026, remediation deadline for the flaw. Microsoft disclosed the vulnerability on November 10, 2026, identifying it as a spoofing issue in Microsoft Outlook. The flaw affects Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024 across supported 32-bit and x64 configurations.

Microsoft rates the maximum severity of the vulnerability as Moderate, despite confirmed attacks targeting the flaw. Microsoft lists a CVSS 3.1 base score of 6.5 for the vulnerability, with low attack complexity and required user interaction. The advisory maps the flaw to CWE-356, described as a failure of the product interface to warn users of unsafe actions. An unauthenticated attacker could send a specially crafted message file and convince a user to open it in an affected version of Microsoft Outlook.

Opening the file could cause Outlook to connect to an attacker-controlled network location without displaying the usual external-content warning. This connection could disclose the user's NTLMv2 authentication hash to the attacker. The attacker could then use the disclosed hash to authenticate as the user.

Who is affected — Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021, and Microsoft Office LTSC 2024 are affected by the vulnerability.

Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021, and Microsoft Office LTSC 2024 are affected by the vulnerability. The affected products include supported 32-bit and x64 configurations. The vulnerability allows an unauthorized attacker to perform spoofing over a network in Microsoft Outlook. Attackers can steal Windows authentication information through a malicious message file.

What to do — IT and patching teams should update Microsoft 365 Apps for Enterprise to the version specified in the Microsoft Office Security Releases pa…

Now

  • IT and patching: IT and patching teams should update Microsoft 365 Apps for Enterprise to the version specified in the Microsoft Office Security Releases page to address the vulnerability. IT and patching teams should update Microsoft Office LTSC 2021 to version 16.0.14334.21048 to apply the fix. IT and patching teams should update Microsoft Office LTSC 2024 to version 16.0.17932.21140 to apply the fix.
  • Security operations: Security operations teams should apply mitigations in accordance with vendor instructions to ensure compliance with CISA’s BOD 26-04 guidance.
  • Leadership and communications: Leadership and communications teams should ensure federal agencies act by November 24, 2026, to meet the CISA remediation deadline.

Next

  • Security operations: Security operations teams should evaluate each asset's internet exposure to ensure adherence to BOD 26-04 patching guidelines.
How solid this is, and what is missing — Microsoft's security advisory and two independent reports from gbhackers.com confirm the existence and details of the vulnerability.

Microsoft's security advisory and two independent reports from gbhackers.com confirm the existence and details of the vulnerability. The reporting is consistent across sources, with no confirmed disagreements regarding the nature of the flaw or the affected products. Microsoft's official record provides the primary technical details, including the CVSS score and severity rating, which are corroborated by the derivative reporting. The CISA catalog entry, reported on November 10, 2026, confirms the active exploitation status and the specific remediation deadline for federal agencies.

No confirmed disagreements between outlets were identified. No timeline updates were identified.

ATT&CK techniques observed — 4 techniques
IDTechniqueEvidence
T1114.002Remote Email Collectionnone quoted
T1204User Executionnone quoted
T1210Exploitation of Remote Servicesnone quoted
T1212Exploitation for Credential Accessnone quoted
Indicators of compromise — No indicators have been published in current sources.

No indicators have been published in current sources.

Detection and hunting — No detection or hunting guidance has been published in current sources.

No detection or hunting guidance has been published in current sources.

Timeline and references — 5 dated entries
DateEventSource
2026-11-10Microsoft Outlook contains a spoofing vulnerability identified as CVE-2026-124194.msrc.microsoft.com
2026-11-10Microsoft patched an actively exploited Outlook zero-day vulnerability tracked as CVE-2026-124194.gbhackers.com
2026-11-10The CISA entry for CVE-2026-124194 was added on November 10, 2026, and establishes a November 24 remediation deadline.gbhackers.com
Reported 2026-11-11Microsoft lists a CVSS 3.1 base score of 6.5 and temporal score of 6.2 for the vulnerability.gbhackers.com
Reported 2026-11-11Microsoft rates the maximum severity of the vulnerability as Moderate.gbhackers.com

Back to top

Story 3 of 6

CVE-2026-125350: Google Chrome use after free

  • New
  • CVE-2026-125350
  • CVSS 8.8
  • In CISA KEV

Bottom line

CISA added a Google Chrome use-after-free vulnerability to its Known Exploited Vulnerabilities catalog on November 10, 2026, stating that attackers are already using the flaw. Google shipped the patch for the vulnerability on November 9, 2026.

StoryCVE-2026-125350: Google Chrome use after free
AffectedGoogle Chrome
SeverityCVSS 8.8 (v3.1)
CISA KEVListed, added 2026-11-10
ExploitationNo attack activity reported in current sources
CoverageNew story
Outlets reporting2
New since last covered13 of 13 facts
What happened — CISA added a Google Chrome vulnerability to its Known Exploited Vulnerabilities catalog on November 10, 2026.

CISA added a Google Chrome vulnerability to its Known Exploited Vulnerabilities catalog on November 10, 2026. According to CISA, attackers are already using the flaw. The vulnerability, tracked as CVE-2026-125350, is a use-after-free bug in Chrome’s XML component. HKCERT says some vulnerabilities in the update could allow denial of service, security restriction bypass, and remote code execution.

Google issued a security update to Chrome’s Stable channel for Windows, Mac, and Linux on November 9, 2026. Google also released Chrome 157.0.8103.50 for Android on November 9, 2026. Google says it was notified about the vulnerability by an unnamed third party on November 6, 2026.

Who is affected — No details yet about who is affected from current sources.

No details yet about who is affected from current sources.

What to do — IT and patching teams must update Google Chrome to version 157.0.8103.50 on Windows, Mac, and Linux immediately.

Now

  • IT and patching: IT and patching teams must update Google Chrome to version 157.0.8103.50 on Windows, Mac, and Linux immediately.

Next

  • IT and patching: IT and patching teams should evaluate each asset's internet exposure to prioritize patching efforts as required by CISA's BOD 26-04 guidance.
  • Security operations: Security operations teams should verify that all Chrome installations are running version 157.0.8103.50 or later to confirm the fix is applied.
  • Leadership and communications: Leadership and communications teams must ensure federal agency assets are patched by 2026-11-24 in accordance with CISA's BOD 26-04 guidance.
How solid this is, and what is missing — Two outlets, cybersecuritynews.com and malwarebytes.com, are reporting on the vulnerability.

Two outlets, cybersecuritynews.com and malwarebytes.com, are reporting on the vulnerability. The claim that attackers are already using the vulnerability is attributed to CISA. Google was notified about a vulnerability by an unnamed third party on November 6. No confirmed disagreements between outlets were identified.

No timeline updates were identified. Who is affected is not yet known from current sources. Nothing in current sources says whether it is being exploited or who is behind it.

ATT&CK techniques observed — No ATT&CK techniques were identified in current sources.

No ATT&CK techniques were identified in current sources.

Indicators of compromise — No indicators have been published in current sources.

No indicators have been published in current sources.

Detection and hunting — No detection or hunting guidance has been published in current sources.

No detection or hunting guidance has been published in current sources.

Timeline and references — 5 dated entries
DateEventSource
2026-11-06Google was notified about a vulnerability by an unnamed third party on November 6.malwarebytes.com
2026-11-09Google shipped the patch for the vulnerability on November 9, 2026.cybersecuritynews.com
2026-11-09Google issued a security update to Chrome’s Stable channel for Windows, Mac, and Linux on November 9.malwarebytes.com
2026-11-09Google released Chrome 157.0.8103.50 for Android on November 9.malwarebytes.com
2026-11-10CISA added the flaw to the catalog on November 10, 2026.cybersecuritynews.com

Back to top

Story 4 of 6

Hackers Compromise Nearly 5,000 GitHub Accounts to Steal Secrets From Software Development Pipelines

  • New in thread

Bottom line

Since November 10, 2026, a threat actor has used stolen GitHub credentials to push a credential-stealing payload into tens of thousands of repositories, targeting software development secrets and cloud access. Organizations should immediately search commits made since November 10 for specific messages such as 'ci: refresh build cache' and 'chore: add dependency audit workflow' to identify and remove the malicious changes. Security teams must also review AWS CloudTrail for unauthorized access events and remove any IAM user access keys created since November 10 to prevent the attacker from maintaining long-lived backdoors in cloud accounts.

StoryHackers Compromise Nearly 5,000 GitHub Accounts to Steal Secrets From Software Development Pipelines
AffectedVersion 3.14.3 of the Packagist package digitalelvis/neuronai-studio is malicious.
SeverityNo CVE for this story
CISA KEVNo CVE for this story
Exploitation1 reported point on attack activity (see What happened)
CoverageNew development in an ongoing thread
Outlets reporting8
New since last covered38 of 38 facts
What happened — A threat actor used stolen GitHub credentials to push a credential-stealing payload into tens of thousands of repositories starting on Nove…

A threat actor used stolen GitHub credentials to push a credential-stealing payload into tens of thousands of repositories starting on November 10. The attack relies on valid tokens belonging to developer and bot accounts rather than exploiting a bug in GitHub Actions. The attacker placed the malware in existing or new GitHub Actions workflows, shell scripts run by CI systems, and npm installation hooks. The stealer collects GitHub Actions secrets, runner memory, and cloud credentials.

The payload sends data by HTTP POST to port 8080 on 194.150.166[.]244, 18.143.168[.]96 or 153.75.82[.]159, or to a Telegram chat. The credential stealer creates new AWS access keys and edits role trust policies, with sessions named wfx-<pid>. Attackers used stolen GitHub credentials belonging to 4,837 accounts to probe 61,764 repositories. GitHub searches identified 61,839 matching pull requests between November 10 at 12:45 UTC and November 11 at 15:00 UTC.

As of November 12, GitHub search returns more than 62,000 of the attacker's probe pull requests, about 90% of them still open. Since about 05:30 UTC on November 12, new copies of the stealer send stolen data to a Telegram chat and carry no collection IP at all. The stealer also reached 28 WebdriverIO repositories through commits authored as the bot account wdio-bot. Automated publishing triggers carried the payload into Packagist package digitalelvis/neuronai-studio 3.14.3 and Go module /onuragtas/docker-env v1.0.278 and v1.0.280.

StepSecurity traced 173 probe pull requests to tokens issued to the Fly[.]io GitHub app.

Who is affected — The malicious payload is included in version 3.14.3 of the Packagist package digitalelvis/neuronai-studio, as well as in versions v1.0.278…

The malicious payload is included in version 3.14.3 of the Packagist package digitalelvis/neuronai-studio, as well as in versions v1.0.278 and v1.0.280 of the Go module github[.]com/onuragtas/docker-env. The stealer reached 28 WebdriverIO repositories through commits authored as the bot account wdio-bot, and at least one Packagist package and one Go module through automated publishing triggers. At least 50 compromised users publish packages across npm, Go, Packagist, PyPI, or crates. In more than 1,800 repositories, the malware ran and shipped GitHub Actions secrets and cloud credentials to the attacker.

The malware gathers GitHub Actions secrets, runtime tokens, cloud credential files, shell histories, and keys for AI tools such as OpenAI, Anthropic, Cursor, and Copilot. The company advises treating any machine that installed or opened the malicious Packagist package as compromised, and the bot account's token should be treated as stolen.

What to do — Security operations teams should search commits made since November 10 for specific messages such as 'ci: refresh build cache' and 'chore:…

Now

  • IT and patching: IT and patching teams should remove the malicious payload from Go module /onuragtas/docker-env versions v1.0.278 and v1.0.280 to prevent further compromise.
  • Security operations: Security operations teams should search commits made since November 10 for specific messages such as 'ci: refresh build cache' and 'chore: add dependency audit workflow' to identify malicious changes. Security operations teams should review AWS CloudTrail for UpdateAssumeRolePolicy and CreateAccessKey events originating from a GitHub OIDC session to detect unauthorized access. Security operations teams should identify and remove any IAM user access keys created since November 10 that are associated with the attack. Security operations teams should inspect AWS role trust policies for entries that allow any AWS principal, which indicate a backdoor created by the stealer.

Next

  • Security operations: Security operations teams should monitor GitHub Audit Logs for deleted workflow runs, as the attacker deletes these to cover their tracks but the activity remains visible in the logs.
How solid this is, and what is missing — No confirmed disagreements between outlets were identified.

No confirmed disagreements between outlets were identified. No timeline updates were identified. No fix or workaround has been published yet in current sources.

ATT&CK techniques observed — 12 techniques
IDTechniqueEvidence
AML.T0090OS Credential Dumpingexfiltrates secrets and cloud credentials
AML.T0091.000Application Access Tokenattacker used stolen GitHub tokens to inject a credential stealer
T1134.001Token Impersonation/Theftnone quoted
T1195.001Compromise Software Dependencies and Development Toolsnone quoted
T1204.005Malicious Librarynone quoted
T1212Exploitation for Credential Accessnone quoted
T1213.003Code Repositoriesnone quoted
T1567.001Exfiltration to Code Repositorynone quoted
T1586.003Cloud Accountsnone quoted
T1589.001Credentialsnone quoted
T1593.003Code Repositoriesnone quoted
T1677Poisoned Pipeline Executionnone quoted
Indicators of compromise — 10 defanged indicators
TypeIndicatorRoleOutlet
ipv4194[.]150[.]166[.]244unknownsafedep.io
ipv418[.]143[.]168[.]96attacker_infrastructuresafedep.io
ipv4153[.]75[.]82[.]159attacker_infrastructuresafedep.io
sha25689695abb392d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cfunknownthehackernews.com
urlhxxp[://]18[.]143[.]168[.]96:8080/exfilattacker_infrastructurethehackernews.com
urlhxxp[://]194[.]150[.]166[.]244:8080/exfilattacker_infrastructurethehackernews.com
ipv4193[.]32[.]204[.]199attacker_infrastructureaikido.dev
domainapi[.]telegram[.]orgunknownstepsecurity.io
ipv4216[.]126[.]225[.]129unknownstepsecurity.io
sha1ee6e5addfe591923fc385553cb66cf0d25634a6bunknownstepsecurity.io
Detection and hunting — Users should search commits since November 10 for specific commit messages like 'ci: refresh build cache', 'ci: restore', 'ci: cleanup', 'c…

Users should search commits since November 10 for specific commit messages like 'ci: refresh build cache', 'ci: restore', 'ci: cleanup', 'chore: add ci helper' and 'chore: add dependency audit workflow', according to StepSecurity. For AWS, users should look for role trust policies containing "Principal": {"AWS": "*"} and for IAM user access keys created since November 10, according to StepSecurity, and CloudTrail events from a GitHub OIDC session. CloudTrail UpdateAssumeRolePolicy and CreateAccessKey events from a GitHub OIDC session are the signal for AWS detection, according to StepSecurity. The payload sends data by HTTP POST to port 8080 on 194.150.166[.]244, 18.143.168[.]96, or 153.75.82[.]159, or to a Telegram chat, according to SafeDep.

The SHA-256 hash of the stealer script is 89695abb392d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cf, according to The Hacker News. Although Wfx deletes workflow runs to cover its tracks, the activity remains visible in StepSecurity's GitHub Audit Log, according to StepSecurity.

Timeline and references — 5 dated entries
DateEventSource
2026-11-10A threat actor used stolen GitHub credentials to push a malicious workflow payload into tens of thousands of repositories starting on November 10.aikido.dev
2026-11-10An attacker has been using stolen GitHub tokens to push a CI secret stealer into repositories since November 10, 2026.stepsecurity.io
2026-11-10Users should search commits since November 10 for specific commit messages like 'ci: refresh build cache' and 'chore: add dependency audit workflow'.stepsecurity.io
2026-11-12Since about 05:30 UTC on November 12, new copies of the stealer send stolen data to a Telegram chat.stepsecurity.io
2026-11-12As of November 12, GitHub search returns more than 62,000 of the attacker's probe pull requests.stepsecurity.io

Back to top

Story 5 of 6

Hackers use AntiFox AI agents in AWS credential-theft attacks

  • New

Bottom line

Attackers are using AntiFox, an open-source AI penetration-testing platform, to compromise web applications and steal Amazon Web Services credentials. Organizations with internet-facing web services and AWS environments should care because the activity involves confirmed malicious actions against these assets, including the use of valid AWS identities to access production secrets. Security teams should immediately audit AWS environments for unauthorized use of IAM users and assumed EC2 roles and review logs for ASPX web shell activity on internet-exposed Microsoft Internet Information Services servers.

StoryHackers use AntiFox AI agents in AWS credential-theft attacks
AffectedNot yet known from current sources
SeverityNo CVE for this story
CISA KEVNo CVE for this story
Exploitation3 reported points on attack activity (see What happened)
CoverageNew story
Outlets reporting4
New since last covered17 of 17 facts
What happened — Arctic Wolf Labs published research detailing how attackers are abusing AntiFox, an open-source AI penetration-testing platform, to comprom…

Arctic Wolf Labs published research detailing how attackers are abusing AntiFox, an open-source AI penetration-testing platform, to compromise web applications and access Amazon Web Services production secrets. The research attributes the activity to Alibaba Cloud infrastructure hosting AntiFox interfaces, linking those systems to malicious actions against internet-facing applications and associated AWS environments. Attackers are using Alibaba Cloud to host self-managed instances of AntiFox to target web services and AWS environments. The activity chains web exploitation and web shell deployment to facilitate configuration discovery and credential validation.

In an observed intrusion, attackers deployed an ASPX webshell on an internet-exposed Microsoft Internet Information Services server. The IIS worker process created the ASPX web shell and then ran commands to gather information about the system. For cloud access, attackers used valid AWS identities, including IAM users and assumed EC2 roles. In one intrusion, attackers moved through multiple AWS identities and issued hundreds of API requests in approximately 30 minutes.

In a separate incident, the attackers used a valid AWS identity to read, copy, and delete S3 objects. The threat actor is said to have started with a valid AWS credential obtained through as-yet-undetermined means in other attacks.

Who is affected — Attackers have used the agentic penetration testing platform AntiFox to steal Amazon Web Services credentials and pivot laterally into comp…

Attackers have used the agentic penetration testing platform AntiFox to steal Amazon Web Services credentials and pivot laterally into compromised environments. In several intrusions, Alibaba Cloud systems hosting AntiFox interfaces were tied to confirmed attacks on internet-facing web services and the AWS environments behind them. According to AWS, its services were not compromised and operated as designed, with attackers using credentials taken from customers’ compromised applications to access their accounts.

What to do — Security operations should immediately review logs for unauthorized ASPX web shell creation and execution by the IIS worker process on inte…

Now

  • IT and patching: IT and patching teams should immediately audit AWS environments for the use of valid IAM users and assumed EC2 roles to identify and revoke any compromised credentials.
  • Security operations: Security operations should immediately review logs for unauthorized ASPX web shell creation and execution by the IIS worker process on internet-exposed Microsoft Internet Information Services servers.

Next

  • Security operations: Security operations should next implement monitoring for agentic penetration testing tools like AntiFox to detect automated credential harvesting and cloud service enumeration, as attackers are using Alibaba Cloud to host self-managed instances of AntiFox to target web services and AWS environments.
How solid this is, and what is missing — Four outlets reported on the activity, with BleepingComputer providing the original account and The Hacker News, Security Affairs, and Cybe…

Four outlets reported on the activity, with BleepingComputer providing the original account and The Hacker News, Security Affairs, and CyberSecurity News offering corroborating or derivative coverage. The core narrative that attackers are using AntiFox to target AWS environments is consistently reported across all four sources. The specific detail that an ARTEX build without a dedicated secrets scanner found eight of nine planted credentials is reported only by CyberSecurity News. The claim that the threat actor started with a valid AWS credential obtained through as-yet-undetermined means is hedged as alleged in The Hacker News report.

No confirmed disagreements between outlets were identified. No timeline updates were identified. No fix or workaround has been published yet in current sources.

ATT&CK techniques observed — 8 techniques
IDTechniqueEvidence
AML.T0075Cloud Service Discoveryenumerate services like S3, Lambda, and Secrets Manager
T1212Exploitation for Credential Accessnone quoted
T1526Cloud Service Discoverynone quoted
T1583.007Serverlessnone quoted
T1584.007Serverlessnone quoted
T1586.003Cloud Accountsnone quoted
T1648Serverless Executionnone quoted
T1651Cloud Administration Commandnone quoted
Indicators of compromise — 2 defanged indicators
TypeIndicatorRoleOutlet
ipv447[.]79[.]4[.]33attacker_infrastructurecybersecuritynews.com
ipv48[.]208[.]101[.]210attacker_infrastructurecybersecuritynews.com
Detection and hunting — In an observed intrusion, the IIS worker process, w3wp.exe, created an ASPX web shell and then ran commands to gather information about the…

In an observed intrusion, the IIS worker process, w3wp.exe, created an ASPX web shell and then ran commands to gather information about the system, according to Security Affairs. For cloud access, attackers used valid AWS identities, including IAM users and assumed EC2 roles, according to Cybersecurity News. In an observed intrusion, attackers deployed an ASPX webshell on an internet-exposed Microsoft Internet Information Services server, according to Cybersecurity News. An ARTEX build without a dedicated secrets scanner found eight of nine planted credentials using ordinary commands, according to Cybersecurity News.

The IP address 47[.]79[.]4[.]33 is identified as attacker infrastructure. The IP address 8[.]208[.]101[.]210 is identified as attacker infrastructure.

Timeline and references — 5 dated entries
DateEventSource
Reported 2026-11-11In one intrusion, attackers moved through multiple AWS identities and issued hundreds of API requests in approximately 30 minutes.securityaffairs.com, cybersecuritynews.com
Reported 2026-11-11Alibaba Cloud systems hosting AntiFox interfaces were associated with confirmed malicious actions against internet-facing web services and associated AWS environments.bleepingcomputer.com, thehackernews.com
Reported 2026-11-11Attackers are using Alibaba Cloud to host self-managed instances of AntiFox to target web services and AWS environments.bleepingcomputer.com
Reported 2026-11-11In a separate incident, the attackers used a valid AWS identity to read, copy, and delete S3 objects.bleepingcomputer.com
Reported 2026-11-11An emerging agentic penetration testing platform called AntiFox has been used to steal Amazon Web Services (AWS) credentials.thehackernews.com

Back to top

Story 6 of 6

CVE-2026-114146: Microsoft .NET 10.0 installed on Linux

  • New
  • CVE-2026-114146
  • CVSS 9
  • Not in KEV

Bottom line

Microsoft released a security advisory on 2026-11-10 for a new elevation of privilege vulnerability in ASP.NET Core, identified as CVE-2026-114146. The flaw allows an authorized attacker to elevate privileges over a network due to incorrect authorization in the framework. IT teams should immediately update Microsoft .NET 10.0 on Linux to version 10.0.15 to mitigate the risk.

StoryCVE-2026-114146: Microsoft .NET 10.0 installed on Linux
AffectedMicrosoft .NET 10.0 installed on Linux .NET 10.0 installed on Mac OS .NET 10.0 installed on Windows .NET 11.0 installed on Linux .NET 11.0 installed on Mac OS .NET 11.0 installed on Windows .NET 8.0 installed on Linux .NET 8.0 installed on Mac OS .NET 8.0 installed on Windows .NET 9.0 installed on Linux .NET 9.0 installed on Mac OS .NET 9.0 installed on Windows Microsoft Visual Studio 2022 version 17.14 Microsoft Visual Studio 2026 version 18.11 Microsoft Visual Studio 2026 version 18.12 Microsoft.AspNetCore.Http.Connections
SeverityCVSS 9 (v3.1)
CISA KEVNot listed
ExploitationNo attack activity reported in current sources
CoverageNew story
Outlets reporting1
New since last covered7 of 7 facts
What happened — Microsoft released a security advisory on 2026-11-10 for a new vulnerability in ASP.NET Core.

Microsoft released a security advisory on 2026-11-10 for a new vulnerability in ASP[.]NET Core. The flaw, identified as CVE-2026-114146, allows an authorized attacker to elevate privileges over a network, as stated by the outlet. The root cause is incorrect authorization within the ASP[.]NET Core framework.

Who is affected — Microsoft released a new security vulnerability on 2026-11-10 affecting ASP.NET Core.

Microsoft released a new security vulnerability on 2026-11-10 affecting ASP[.]NET Core. The vulnerability allows for elevation of privilege.

What to do — IT and patching teams should update Microsoft .NET 10.0 installed on Linux to version 10.0.15 immediately.

Now

  • IT and patching: IT and patching teams should update Microsoft .NET 10.0 installed on Linux to version 10.0.15 immediately. IT and patching teams should update Microsoft .NET 10.0 installed on Mac OS to version 10.0.15 immediately. IT and patching teams should update Microsoft .NET 10.0 installed on Windows to version 10.0.15 immediately.
How solid this is, and what is missing — Microsoft's own security advisory is the sole source reporting this vulnerability, with no independent media coverage or third-party confir…

Microsoft's own security advisory is the sole source reporting this vulnerability, with no independent media coverage or third-party confirmation identified in the available records. The source describes the vulnerability as a new security vulnerability released on 2026-11-10, using definitive language rather than hedges such as alleged or reportedly. No confirmed disagreements between outlets were identified. No timeline updates were identified.

Nothing in current sources says whether it is being exploited or who is behind it.

ATT&CK techniques observed — 2 techniques
IDTechniqueEvidence
T1212Exploitation for Credential Accessnone quoted
T1689Downgrade Attacknone quoted
Indicators of compromise — No indicators have been published in current sources.

No indicators have been published in current sources.

Detection and hunting — No detection or hunting guidance has been published in current sources.

No detection or hunting guidance has been published in current sources.

Timeline and references — 2 dated entries
DateEventSource
2026-11-10A new security vulnerability was released on November 10, 2026, affecting ASP[.]NET Core.msrc.microsoft.com
2026-11-10A new security vulnerability in ASP[.]NET Core allows for elevation of privilege.msrc.microsoft.com

Back to top