Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #4217

O

Orca Security

Company blog · orca.security/resources/blogsecurity

Orca Security is the company blog at orca.security, writing about security. Since 2020, 18 different Hacker News readers have linked it 21 times, most often “SynLapse – Technical Details for Critical Azure Synapse Vulnerability”. It is still writing: the last post was on 2026-10-28, and you can follow it by feed.

Visit the blog
21mentions?
18HN people?
2020–2026first – last linked?
Links on Hacker News per year · peak 10 in 2022

Too few sampled comments (5) to say how often HN recommends it.?

Why HN links it

HN commenters link Orca Security's research posts on cloud and developer-tool vulnerabilities, including AWS CloudFormation and AWS Glue flaws, Azure Automation cross-tenant access, and GitHub Codespaces token scoping.

Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Secure your multi-cloud environment from build to runtime with the industry-leading CNAPP. Featuring comprehensive AI security and workload defense.

Most-linked posts?

  1. SynLapse – Technical Details for Critical Azure Synapse Vulnerability
    3 people · 3 mentions · first linked 2022-06-14
  2. AWS Superglue Vulnerability
    2 people · 2 mentions · first linked 2022-01-13
  3. BreakingFormation: AWS CloudFormation Vulnerability
    2 people · 2 mentions · first linked 2022-01-13
  4. Critical cross-account vulnerability in Microsoft Azure automation service
    2 people · 2 mentions · first linked 2022-03-07

What Hacker News says?

  1. Seems like the AWS Glue exploit [1] discovered by the same team is the more critical one of these two. The CTO of Orca confirmed that they were able to access an admin role in an AWS service account, and from there assume roles in customer accounts with service roles that trust the glue service [2]. 1: https://orca.security/resources/blog/aws-glue-vulnerability/ 2: https://twitter.com/yoavalon/status/148169107567269…

    Comment linking /resources/blog/aws-glue-vulnerability/

    on “BreakingFormation: AWS CloudFormation Vulnerability”
  2. Submitted Palo Alto Networks sends cease-and-desist letter to take down review videos as a story · 457 points

    HN discussion
  3. If you really want access to the execution engine, looks like one team found a way. https://orca.security/resources/blog/aws-cloudformation-vuln...

    Comment linking /resources/blog/aws-cloudformation-vulnerability/

    on “AWS Announces the General Availability of AWS CloudFormation Hooks”
  4. Submitted Critical cross-account vulnerability in Microsoft Azure automation service as a story · 216 points

    HN discussion
  5. https://windowsforum.com/security-alerts.84/cve-2025-55241-e... https://orca.security/resources/blog/autowarp-microsoft-azur... https://petri.com/microsoft-azure-automation-cross-tenant-ac... I don’t recall much in the way of AWS vulnerabilities like these, but they’re a regular occurrence on Azure.

    Comment linking /resources/blog/autowarp-microsoft-azure-automation-service-vulnerability/

    on “Kimi-K3 Releases on HuggingFace 6/27”
  6. Submitted BreakingFormation: AWS CloudFormation Vulnerability as a story · 90 points

    HN discussion
  7. > it'd be awesome if the in-browser IDE launched with a temporary per-repo permission scope That's actually exactly what they do for codespaces. The token only has read/write on the repo you activated for the codespace [1]. They should definitely consider doing that for github.dev as well. [1] https://orca.security/resources/blog/hacking-github-codespac...

    Comment linking /resources/blog/hacking-github-codespaces-rce-supply-chain-attack/

    on “1-Click GitHub Token Stealing via a VSCode Bug”
  8. Submitted AWS Superglue Vulnerability as a story · 43 points

    HN discussion
  9. In agreement with frodd above. Dependencies and supply chain attacks are probably the greatest risk to a lot of software orgs, as they run them across all their environments: Development (with secrets and other valuable artefacts on developer VMs), CI/CD pipelines which may have access tokens to production (and other) environments, and production itself. Notably even security companies are being impacted by this[0].…

    Comment linking /resources/blog/hades-pypi-supply-chain-attack/

    on “Vulnerability Reports are not Special Anymore”
  10. Submitted SynLapse – Technical Details for Critical Azure Synapse Vulnerability as a story · 9 points

    HN discussion
  11. Submitted SynLapse – Technical Details for Critical Azure Synapse Vulnerability as a story · 5 points

    HN discussion
  12. Submitted Security Advisory: Insufficient Tenant Separation in Azure Synapse Service as a story · 5 points

    HN discussion
  13. Submitted 'Leaky Vessels' Docker Vulnerabilities Found in Many Cloud Environments as a story · 3 points

    HN discussion
  14. Submitted Microsoft's July 2026 Patch Tuesday fixes 622 CVEs, 2 exploited zero-days as a story · 2 points

    HN discussion
  15. Submitted How the Sys:All Loophole Allowed Us to Penetrate GKE Clusters in Production as a story · 2 points

    HN discussion
  16. Submitted Splunk Enterprise Vulnerabilities Allow Unauthenticated File Operations as a story · 1 points

    HN discussion
  17. Submitted Watch the Typo: PoC Exploit for Typosquatting in GitHub Actions as a story · 1 points

    HN discussion
  18. Submitted How the Sys:All Loophole Allowed Us to Penetrate GKE Clusters in Production as a story · 1 points

    HN discussion
  19. Submitted The Cloud Risk Encylopedia as a story · 1 points

    HN discussion
  20. Submitted SynLapse – Technical Details for Critical Azure Synapse Vulnerability as a story · 1 points

    HN discussion
  21. Submitted Palo Alto Customers Deserves Better as a story · 1 points

    HN discussion

Search all of HN for orca.security

Linked by the same people?