monorepo

I don't think this is the same issue as the exploit. The real issue was half-caught in a review on a pull request however. https://github.com/nomad-xyz/monorepo/pull/289/files If this legacy enum value had been handled later in the code, there would not have been a vulnerability. (This isn't to say that the developers were bad. The person who wrote the code was extremely knowledgeable. It's just really hard to be perfect every time. )

I've been harping on this part of DeFi for a long time... developers should be writing very good tests. Along with that, security reviews should be followed. This is the review in question [1] where developers ignored the possibility of an issue. This is the commit [2] that likely caused the issue, no tests added. Along with a large chunk of "never brag about your security" hubris [3]. [1] https://news.ycombinator.com/item?id=32319344 [2] https://github.com/nomad-xyz/monorepo/commit/46d14571f3eada6... [3] https://twitter.com/0xemon/status/1554310755071119361