BlackTree Security · Infrastructure · Automation · AI

BlackTree — Independent Technology Analysis

BlackTree Editorial

Independent technology intelligence Analysis · Technical guides · Homelab · Legacy systems

Security, systems and emerging technology

Know the signal behind the incident.

Independent analysis for the people who build, secure and operate technology, with the clarity to inform action and the technical depth to earn trust.

Evidence-linked Operational context Independent

AI Regulatory Readiness: What to Do Now and What to Prove in 2027

How to document, test and govern hosted AI, self-hosted models and agents under the AI Act and existing privacy and resilience rules.

Read the article ↗

Current reporting

Latest intelligence

View all articles ↗

Stolen GitHub Tokens Turn Build Workflows Into Secret Stealers

Researchers at Aikido Security, SafeDep and StepSecurity have documented a campaign using stolen GitHub tokens to plant a credential stealer in repositories. Aikido calls the campaign wfx-loot and traces the activity to 10 November. It counted 4,837 compromised accounts that opened probe pull requests in 61,764 repositories. SafeDep counted malicious commits in 8,093 repositories in its own search window. The two counts measure different stages of the campaign. Aikido’s disclosure · SafeDep’s analysis

The attacker tests repository access with a pull request titled docs: dependency audit notes from a branch called wfx-docs. A probe identifies a repository worth investigating. To find evidence that the stealer ran, check later pushes by the same account, including automation accounts that can bypass branch protection. Researchers found the payload in existing and newly created workflows, ordinary shell scripts used by CI and npm lifecycle hooks. Aikido’s campaign timeline · StepSecurity’s repository analysis

An attacker may revert a change and delete the associated Actions run. Compare the repository’s audit and push records with the workflow history, and use retained runner or cloud logs to investigate any gap. StepSecurity documented a surviving run in which the stealer collected data from a self-hosted runner. A successful workflow status can coexist with malicious activity. StepSecurity’s investigation

Preserve evidence, stop suspicious workflows and revoke the GitHub token used to make the unauthorised push. If the payload ran, rotate credentials the job could access, including registry and deployment tokens and secrets available on self-hosted runners. Review cloud audit logs for…

12 Nov 2026 · 2 min read

Check Point Traces a Gateway Intrusion to an ESXi Wiper

Check Point has disclosed attacks in which an unpatched Mobile Access portal became a route into a customer network. In one investigation, the attacker exploited PHP2Shell on the gateway, gained root through…

12 Nov 2026 · 2 min read

Secure Client’s Posture Flaw Starts With Local Access

Cisco’s Secure Client security update needs an endpoint check that reaches beyond the application’s name. The affected component is Secure Firewall Posture, and the disclosed attack requires an existing local account. Windows,…

12 Nov 2026 · 2 min read

ConnectWise Warns of Rogue ScreenConnect Deployments

ConnectWise is investigating unauthorised access to some partners’ ScreenConnect environments and reports that attackers installed remote-access software on customer devices. In its first public notice, issued at 22:45 UTC on 11 November,…

11 Nov 2026 · 2 min read

Apache Fixes a Critical HTTP/2 Code Execution Flaw

Apache HTTP Server 2.4.71 fixes a critical flaw in its HTTP/2 module. A race while the module handles request headers can corrupt memory and let a remote attacker run code in the…

11 Nov 2026 · 2 min read

Revised reporting

Recently updated

View all articles

Geographic context

Regional intelligence

Browse all articles ↗

Coverage leaders

Vendor intelligence

Browse all articles ↗

Practical archive

Lab &
Legacy

Field-tested guidance for keeping older systems useful, secure and reliable long after mainstream documentation has moved on. Practical fixes, automation and deployment notes are drawn from real environments and written for the operators who still maintain them.