So, @Rapid7Official is shutting down AttackerKB (https://attackerkb.com/) soon.

I view this as a case where an initially promising idea became overwhelmed by low‑quality reports from contributors.

Anyway, archive any data you wish to retain.

@h0ng10 I maintain @attackerkb and I don't see an alarming level of spam. I see this more as one of the last community-driven knowledge-bases turning into a service/product.

@Rapid7Official

@buherator @Rapid7Official @attackerkb

I liked it as a resource for technical vulnerability analysis. The last times that I looked into it, I saw more and more stuff that looked like an incident / report.

I don't know if this is actually the reason Rapid7 shuts it down, but it was the reason why I used it less often. But I don't consider myself as a "power-user"

@h0ng10 @Rapid7Official @attackerkb One nice thing about similar initiatives is that people can use them differently. Some moderation work would've been required for sure, but I don't see that as a major, shutdown triggering problem.