Skip to content
You must be logged in to sponsor Concinnity-Risks

Become a sponsor to Concinnity Risks

@Concinnity-Risks

Concinnity Risks

Concinnity-Risks
Cambridge, England

We have some code for finding cryptocurrency address in ransomware, and doing financial forensics. We like finding vulnerabilities and being able to publish our work. We're a little tired of NDAs preventing a more consumer rights approach to security and privacy testing. So if you would like to see us find vulnerabilities and publish them under a gentle coordinated disclosure, we are open to suggestions. We like Android and networking equipment assessments especially.

We're people who like to work from home, and play with technology. We think writing good code, being good parents, and enjoying a slower lifestyle aren't incompatible. You're as likely to find us out foraging while we structure our thoughts around a problem as you are with our fingers on the keyboards.

Technology excites us, but it isn't usually the solution. We love to tinker, play, expand, and subvert technologies, but we also like people, books, and gardens. Balancing these things make us happy, and we are grateful for the chance to do the work we love.

We like projects chasing corporate corruption, and defunding anti-human behaviours. We aspire to write code for visualising financial inequality, and combating personal debt (especially student debt). We also like cryptocurrency projects and new creative economic models that sustain financial intimacy for small collectives.

Your sponsorship allows us to deviate more from the kinds of projects that are short sighted. It gives us the ability to do things that aren't profit driven, and that have a longer term vision. For example, documenting and curating the ransoms of ransomware was slow, and didn't produce a profit for a year or so. However, it did help build cyber risk models which now help people manage the risk more effectively. Another example is that penetration testing of consumer devices is time consuming and expensive, but why shouldn't the results be more publicly available after they are done (and fixed)? We'd love to do some crowdfunded security assessments, instead of working for one large customer under NDA. It changes the focus of the testing, and we think that has value.

@Concinnity-Risks

We can do bug fixes for RansomCoinPublic. We can also spend more time documenting it well, which often gets ignored at the moment for other paid work.

Featured work

  1. Concinnity-Risks/RansomCoinPublic

    A DFIR tool to extract cryptocoin addresses and other indicators of compromise from binaries.

    Python 57
  2. Concinnity-Risks/LogisticalBudget

    This project contains code for comparing or ranking APT capabilities and operational capacity. The metrics are meant to quantify, rank, order, compare, or visualise quickly threat actors demonstrat…

    Python 35

0% towards $200 per month goal

Be the first to sponsor this goal!

Select a tier

$ one time

Choose a custom amount.