Skip to content
Latest
SafePay Warning: Prove Your Backups Can Survive an Administrator CompromiseTeamUpdraft Compromise: Check Every Connected WordPress Site for PersistenceRailway Secrets Incident: Rotate Credentials, Then Check What They Could ReachLiteLLM 1.107.0 Compromise: Rebuild the Environment, Recover the CredentialsGitLab Regex RCE: Patch the Server, Verify the Delivery ChaineMudhra CA Key Compromise: Check the Trust Stores Beyond Your BrowserPHP2Shell: Patch the Runtime Behind Your WebsitesTrusted Notifications, Untrusted Instructions: Close the Email Content GapBRONZE SANDCASTLE: Hunt the DLL Load Chain, Not the Trusted ExecutableOne Stolen Identity, Several SaaS Platforms: Respond Beyond the MailboxSiemens Software Center ClickFix Attacks: Hunt Beyond the Trusted SignatureBeyondTrust Authentication Bypass: Patch the Appliance, Review the AccessPEERSTITCH: Recover the Management Trust, Not Just the FirewallCikaBika Bot: Detect the Document-to-Discord Attack Chain

IOC Passport

subprocess[.]run

DomainArticle-derived observationCurrent reporting windowReported in 2 articlesWatch this →

A domain extracted from published reporting. It may be infrastructure, a cited service, or a candidate indicator; check current feed admission before blocking. Shown defanged for safe viewing; use Copy live value for the functional form.

This value remains inside its 30-day domain/URL reporting window. Current reporting status is separate from verified-feed admission. Archive-cleared or archived does not mean clean, inactive, benign, remediated, resolved, or safe, and this lifecycle does not change current verified-feed admission.

Current verified-feed status

Checking live guard…

Article reporting and current malicious-feed admission are evaluated separately.

First reported
Last reported
Article count
2
Admission policy
bulwark-exact-malicious-v2
Research lifecycle
Current

Related indicators

Observables that appear alongside this one in the same reporting. Co-occurrence can suggest shared infrastructure, but it does not establish common ownership, campaign identity, or actor attribution.

hmac[.]new0aaf7ba346d41ef2f40390436738b001180d5a1c03aa093f121078a9969d9a1a12d4ccc5c6f8d35cf4f2cf233b7f3e418e863e657d81ff5f5fc9e210005b94841bbce8caa94f01c0aaa0b7ddae51553a8a32e1ce53d96d44fe583272aff7ad0020535d8fa11f786a6c24df7488a0e449ed5f09ad20a59e5a285799e7cf7fa16cfba1c1414f1e84a8459e14207cfd4e998c2cd24b2befe2a79fb4fbbd9a543b5b40b530c8cffa8771bab22b8fb22b2e4ae3b1f81934bef04fe88ac9d0aae0475630b1738681d15b94f233ac8aa46eacf5968305fa462d0c9f67ca522d9e0e4acd245e90b36ce0d5353604a66bb7c43a1ec4a6fcf756b74573eed6e4aafe4b50603dbe7853e0345f188c8e44a09f1098caf1f4bcdf668169d35b87bf51324080390b1b1c5ab12bd335cfe5f1a99e3689abd5e02ae666c8f5b1a9cefaa7c55b758f86f4ab552f2e859e6ea3d8ef6cf73a72d8df24f663b7a31ce67494eeb9b0d707b93484e66675d2df7598727f209d717041db37f7dca271d3a7d328a279890e0e1d55375729aeb86d9dd0a3926f96a37eb86cf1ee2310d9be93139cc4ebef3ef9e2efe9531390be25a898fd08ad220fed52488906eb45d196f332b972ad5d85214e7726545ecc4218asyncio[.]runatomicmail[.]iobd1aeee419ea36da9aa2b657288da4101887be468f020ac63d22ba6ed84a3ea5c2e32d0ce2548aa662c18bf5001911a79fe5b30cf8357132275add02fdcde054CVE-2026-65400datetime[.]datetime[.]nowdocs[.]litellm[.]aif[.]readghcr[.]iogradle[.]propertieshxxp://www[.]litellm[.]dev/healthcheckhxxps://docs[.]litellm[.]ai/blog/security-incident-oct-21-2026#how-this-happenedhxxps://github[.]com/Berri-AI/litellmhxxps://raw[.]githubusercontent[.]com/letters9813/pythonclient-test/main/domain[.]txtlitellm-1[.]107[.]0[.]datalitellm[.]ailitellm[.]devm[.]groupmodels[.]litellm[.]cloudos[.]openr[.]readre[.]searchtarfile[.]opentarget[.]com

Newsletter

The House-Of-L Brief.

Two short reads a day on markets, cyber threats, AI, and geopolitics. A "why it matters" line on every story.

Double opt-in. One-click unsubscribe on every issue. We never share your address.