Vulnerability & exposure · Application & API security

Bugcrowd

United States · bugcrowd.com
Official address, recorded by DBSE. Everything on this page that talks about domains uses these.

Crowdsourced security testing platform.

Community rating

– ★★★★★ 0 ratings
5 ★
0
4 ★
0
3 ★
0
2 ★
0
1 ★
0

Sign in to rate.

Scorecard from 0 structured reviews

Deployment effort
–
Support quality
–
Features vs promises
–
Pricing transparency
–
Return on investment
–

All reviews and filters → · Compare

Exposure signal

Low

An objective, third-party reading of this vendor's own credential hygiene. It is not part of the community scorecard and does not affect any rating on DBSE.

Staff credentials in infostealer logs
5
Third-party services their staff use
15
What those credentials open
business systems

Credentials belonging to 5 of this vendor's own staff appear in infostealer logs, and the most recent staff credential appeared 1 year ago. Their staff hold credentials for 15 distinct external services, which is the surface a successful attack on this vendor could reach. This says nothing about how well the product works.

Customer-side infections: 8,814 (not counted in the band)

These are infections on the machines of people who log in to this vendor's service. They reflect those users' own endpoint hygiene, and a vendor with a large consumer or partner login footprint will always show more of them. Counting that against the vendor would penalise popularity, so this platform does not.

Which of their own systems the exposed credentials open
SystemTimes seen
https://bugcrowd.com/user/sign_in3
https://tracker.bugcrowd.com/mdcoop-og-bb/settings/integrations/jira/5eedfd77-bead-41d8-b9f0-bbfa4bdaf628/authorization2
https://bugcrowd.com/atlassian1

This is the part a count cannot tell you. A stolen credential for a login page that fronts single sign-on or an administrative console reaches further than the same credential for a marketing site, so it carries the smallest of the three weights in the band above. These are the vendor's own published login pages, nothing private.

Context that is recorded but never scored

Stealer families seen against this domain: Vidar, DarkCrystal, CRYPTBOT, Raccoon, StealC, Azorult. Which malware took a credential says more about what is circulating than about the vendor, so it is not scored.

Which third-party services appear · 1 of these is in our directory
ServiceIn our directoryCommunity ratingOccurrences
lightspeed.app Not listed – 4
atlassian.com Not listed – 3
1password.com Not listed – 2
simplify.com Not listed – 2
unity.com Not listed – 1
thousandeyes.com Not listed – 1
kisi.io Not listed – 1
netflix.com Not listed – 1
lieferando.de Not listed – 1
intercom.io Not listed – 1
network-auth.com Not listed – 1
okta.com Okta Not rated yet 1

If your own organisation depends on any of these, a successful attack on this vendor and an attack on you share a blast radius. That is worth a question in the security review, not a reason to walk away. Where a service is itself a vendor in our directory it is named and linked, with whatever the community has scored it, so you can read both sides of the dependency in one place. The rating shown is the community's own; it is not derived from this exposure data.

Two independent sources agree on 5 exposed staff credentials.

Source: FireIntel (xti.fireintel.net), public domain summary. Source: Hudson Rock (hudsonrock.com), free infostealer intelligence API. About this data. Read 1 month ago, and due a refresh. DBSE does not collect, hold, or sell this data.

Discussions about Bugcrowd