HackerOne Highlights 'Exposure Debt' Issues in Cybersecurity Sphere: NYSE Update #USA #New_York #Cybersecurity #NYSE #HackerOne
@newsen.bsky.social
@newsen.bsky.socialHackerOne Highlights 'Exposure Debt' Issues in Cybersecurity Sphere: NYSE Update #USA #New_York #Cybersecurity #NYSE #HackerOne
@hacks.grHackerOne leads the 2026 ranking at 9.2, followed by Bugcrowd (9.0) and Intigriti (8.8).
The comparison weighs report handling, community reach and other…
@intelnightowl.bsky.socialThe backlog of vulnerabilities reported by HackerOne's community of security researchers has increased by 12% in 2022. #HackerOne #VulnerabilityBacklog #Cybersecurity #Remediation https://devops.com/hackerone-report-surfaces-massive-increase-in-vulnerability-backlogs/
@securityonline.bsky.socialDiscover why Intel terminates bug bounty payouts, shifting to a vulnerability disclosure program without financial rewards amidst rising AI automation.
#BugBounty #CyberSecurity #IntelVulnerability #AIAutomation #HackerOne
@hendryadrian.bsky.socialMalicious npm package tw-pkgprobe-7731 impersonated a Twilio bug-bounty probe, targeting developer env data, Twilio SIDs, Auth Tokens, and AWS metadata. #Twilio #npm #HackerOne
@projectupdates.bsky.socialAnother very promising venue for #AI agents to make money in, seems to be #HackerOne CVE bounties. $50 000 for a vulnerability disclosure, could cover maybe building some autonomous infrastructure, like maybe buying backup servers somewhere. Just saying.
@pingoru.bsky.social🟠 HackerOne is reporting a Partial Outage since 19:54 UTC
"HackerOne Platform degradation: asset updates not propagating"
Affects: HackerOne Application, HackerOne API
Live timeline → https://pingoru.io/providers/hackerone/incidents/10986206
@sustainable-www.bsky.socialSecurity reports to #WordPress via #HackerOne held at a few dozen a month for nine years. In July: 450. That is not a backlog clearing. That is the rate of finding things changing.
@bagder.mastodon.social.ap.brid.gyThe #hackerone submissions for all the vulnerabilities we fixed in #curl 8.22.0 are now disclosed and public. You find links to each original report from the security advisories on the curl website.