BetaIT-Hub is in early access — your feedback helps us improve. Use the chat or email [email protected]

Latest
Suspicious Polyfill login prompts pop up on Toshiba, Muji websitesBleepingComputer · 7h agoFormer cyber executive turned whistleblower accuses IBM of covering up several data breachesTechCrunch Security · 8h agoCISA: Hackers now exploit SolarWinds Serv-U flaw to crash serversBleepingComputer · 9h agoMiasma Malware Hits 32 Red Hat Packages via Compromised GitHub AccountHackRead · 9h agoChinese APT deploys new malware to keep access to hacked networksBleepingComputer · 10h agoIronWorm and New Miasma Worm Variant Hit npm in Supply Chain AttacksThe Hacker News · 10h agoDark web Nemesis Market vendor gets 26 years for selling drugsBleepingComputer · 11h agoAtlas Menu Data Breach Exposes 64,000 GTA V and CS2 Cheat Service UsersHackRead · 11h agoWeekly Metasploit Update: Apache ActiveMQ RCE, Gogs Rebase RCE, and Windows Kernel Pointer EnumRapid7 · 11h agoSecuring CI/CD in an agentic world: Claude Code Github action caseMicrosoft Security · 12h agoGoogle and FBI warn of ransomware group that sends fake IT workers to hack victims in personTechCrunch Security · 12h agoAndroid Spyware Asin Targets Arabic Users via Fake News, PDF and War Map AppsThe Hacker News · 14h agoOver 900 US gas station tank gauge systems exposed to attacksBleepingComputer · 14h agoNSA said to be readying Anthropic’s Mythos for use in cyber operationsTechCrunch Security · 14h agoWhat 2026 DBIR Confirms: Attacks Are Living in the BrowserBleepingComputer · 14h agoSuspicious Polyfill login prompts pop up on Toshiba, Muji websitesBleepingComputer · 7h agoFormer cyber executive turned whistleblower accuses IBM of covering up several data breachesTechCrunch Security · 8h agoCISA: Hackers now exploit SolarWinds Serv-U flaw to crash serversBleepingComputer · 9h agoMiasma Malware Hits 32 Red Hat Packages via Compromised GitHub AccountHackRead · 9h agoChinese APT deploys new malware to keep access to hacked networksBleepingComputer · 10h agoIronWorm and New Miasma Worm Variant Hit npm in Supply Chain AttacksThe Hacker News · 10h agoDark web Nemesis Market vendor gets 26 years for selling drugsBleepingComputer · 11h agoAtlas Menu Data Breach Exposes 64,000 GTA V and CS2 Cheat Service UsersHackRead · 11h agoWeekly Metasploit Update: Apache ActiveMQ RCE, Gogs Rebase RCE, and Windows Kernel Pointer EnumRapid7 · 11h agoSecuring CI/CD in an agentic world: Claude Code Github action caseMicrosoft Security · 12h agoGoogle and FBI warn of ransomware group that sends fake IT workers to hack victims in personTechCrunch Security · 12h agoAndroid Spyware Asin Targets Arabic Users via Fake News, PDF and War Map AppsThe Hacker News · 14h agoOver 900 US gas station tank gauge systems exposed to attacksBleepingComputer · 14h agoNSA said to be readying Anthropic’s Mythos for use in cyber operationsTechCrunch Security · 14h agoWhat 2026 DBIR Confirms: Attacks Are Living in the BrowserBleepingComputer · 14h ago

Security & IT News

Live

Real-time news from 13+ trusted sources — BleepingComputer, The Hacker News, Krebs on Security, Dark Reading & more.

VulnerabilityThe Hacker News·71d ago
China-Linked Red Menshen Uses Stealthy BPFDoor Implants to Spy via Telecom Networks

A long-term and ongoing campaign attributed to a China-nexus threat actor has embedded itself in telecom networks to conduct espionage against government networks. The strategic positioning activity, which involves implanting and maintaining stealthy access mechanisms within critical environments, has been attributed to Red Menshen, a threat cluster that's also tracked as Earth Bluecrow,

🩹 PatchSANS ISC·71d ago
TeamPCP Supply Chain Campaign: Update 001 ? Checkmarx Scope Wider Than Reported, CISA KEV Entry, and Detection Tools Available, (Thu, Mar 26th)

This is the first update to the TeamPCP supply chain campaign threat intelligence report, When the Security Scanner Became the Weapon (v3.0, March 25, 2026). That report covers the full campaign from the February 28 initial access through the March 24 LiteLLM PyPI compromise. This update covers developments since publication. Checkmarx ast-github-action: All 91 Tags Were Compromised, Not Just v2.3.28 The most significant new finding since the report s publication: the scope of the Checkmarx ast-github-action compromise was substantially larger than publicly reported. Checkmarx s official security advisory stated that all older versions have been permanently deleted but did not quantify how many tags were affected. This ambiguity allowed the security community to anchor on a single confirmed version (v2.3.28) as the extent of the compromise. Sysdig s analysis characterized it as Checkmarx/ast-github-action/2.3.28: (possibly more). Even Wiz, which assessed that it is likely all tags were impacted, only observed the single tag directly. An independent security researcher who was working this incident firsthand at a Checkmarx customer has now provided primary evidence that all 91 published tags were overwritten every version from v0.1-alpha through v2.3.32. The evidence is publicly visible in the GitHub activity log , which shows 91 tag deletions performed during Checkmarx s remediation between 19:09 and 19:16 UTC on March 23, 2026. Three of the malicious commits are still visible on GitHub: f1d2a3477e0d f58de2470825 aa52a82cddf2 Each malicious commit follows an identical pattern: the legitimate Docker-based action.yml was replaced with a composite action that executes a credential-stealing setup.sh before delegating to the legitimate Checkmarx action at pinned SHA 327efb5d . Each commit was individually crafted with a version-appropriate backdated timestamp and fake commit message (e.g., 2.0.30: PR # ). The attacker did not reuse a single malicious commit across multiple tags they created individual poisoned commits for individual versions. The impact of this under-reporting is material. Organizations that searched their CI/CD logs only for [email protected] would have missed compromised runs referencing any of the other 90 poisoned tags. The credential stealer executed regardless of which tag version was referenced. Recommended action: Search your CI/CD workflow logs for ANY reference to checkmarx/ast-github-action that executed between 12:58 and 19:16 UTC on March 23, 2026. If found, treat all secrets accessible to that workflow as compromised and rotate immediately. The only safe version is v2.3.33, released during remediation. For comparison, the companion kics-github-action received accurate all 35 tags reporting from the outset, largely because GitHub Issue #152 was filed publicly with the title Malware injected in all Git Tags. No equivalent public issue was filed for ast-github-action . CISA Adds CVE-2026-33634 to Known Exploited Vuln

VulnerabilityThe Hacker News·71d ago
[Webinar] Stop Guessing. Learn to Validate Your Defenses Against Real Attacks

Most teams have security tools in place. Alerts are firing, dashboards look clean, threat intel is flowing in. On the surface, everything feels under control. But one question usually stays unanswered: Would your defenses actually stop a real attack? That’s where things get shaky. A control exists, so it’s assumed to work. A detection rule is active, so it’s expected to catch something. But very