In late 2025, an r/MachineLearning thread surfaced an OpenReview profile crediting one individual — Kevin Zhu, affiliated with a program called Algoverse AI Research — with 158 publications across 468 distinct coauthors. The thread, and the public profile data it pointed at, sparked a wider argument about what counts as legitimate authorship in machine learning and what readers should look for when a paper is offered as evidence for a tool, technique, or claim.
This is not a tabloid story about ambitious teenagers. It is a structural story about incentives — how cheap LLM-assisted writing, expanding workshop tracks at major conferences, and a willingness to pay for an "author" slot converge into something the research community has started calling a paper mill.
What the OpenReview profile actually shows
OpenReview hosts peer review for venues including ICLR and a long list of NeurIPS, ICML, and EMNLP workshops. Public profiles list every paper an author is named on. The Zhu profile shows 158 papers and 468 distinct coauthors. For context, even prolific senior researchers in a single lab typically publish on the order of 10 to 20 papers a year, with coauthors who overlap heavily across a stable group of students and collaborators.
A 468-coauthor count without a corresponding lab structure raises the obvious question: how does one researcher meaningfully participate in 158 papers? Commenters on the thread point to Algoverse, an online program that pairs paying participants — many of them high schoolers — with mentors who then submit work to workshops and lower-tier venues.
The complaint from the ML community is not that students are doing research. It is that the program markets ML research authorship as a credential to buy, that the resulting papers cluster at venues where reviewer load is high and acceptance is permissive, and that the volume distorts both the credentialing system used by admissions committees and the literature itself.
Workshop papers and arXiv preprints do not clear the same bar as main-conference papers. When you see a paper cited as "NeurIPS 2024" check whether it appeared at the main conference or at a workshop — the difference is significant, and paper mills disproportionately target the lower-bar venues where one or two reviewers can be overwhelmed by submission volume.
Why developers evaluating AI tools should care
When a startup pitches you on a new model, retrieval technique, agent framework, or evaluation harness, the claim is usually backed by a paper. You skim the abstract, glance at the author list, maybe note the affiliations. That heuristic — real authors at real institutions, peer-reviewed venue — has been one of the few cheap signals separating substantive work from marketing copy dressed up in LaTeX.
Paper mills weaken that signal in two ways. First, they pollute the citation graph with low-quality work that gets cited downstream because reviewers, search engines, and LLM-based literature tools cannot easily tell the difference between a 12-author workshop paper and a 4-author main-conference paper from a known lab. Second, they normalize the idea that authorship is a transferable commodity, which makes it harder to take any given paper's results at face value even when the work is genuinely original.
If you are choosing between two embedding libraries and one cites a paper with 14 coauthors you have never heard of, published at a workshop you have never heard of, with the same senior author appearing on dozens of other recent submissions — that is information. It does not automatically mean the technique is wrong. It does mean the burden of independent verification has shifted onto you.
How to read author lists like a reviewer
A practical checklist when a paper is offered as evidence for a tool's claims:
- Check the venue tier. Main-conference papers at NeurIPS, ICML, ICLR, CVPR, and ACL clear a higher bar than workshops at those same conferences. Workshops at smaller venues clear a lower bar still. arXiv-only papers have no peer review at all.
- Look at coauthor patterns. Open Google Scholar or OpenReview for the senior author. If they have hundreds of papers in two years with non-overlapping student lists, treat the work as a structural prior rather than a personal endorsement.
- Read the code, not the abstract. Reproducible work ships a repository with weights, training scripts, and an evaluation harness. Paper mill output disproportionately skips this step or provides a repo that does not match the paper's claims.
- Check the dataset. Real contributions usually involve new data or a clearly justified subset of an existing benchmark. Generic MMLU subsets with no rationale are a tell.
- Search for replications. Genuine results get replicated, cited critically, and built on. If a paper is two years old with three citations, none of which extend it, the technique may not have worked outside the original setup.
The broader incentive problem
Algoverse is one specific program, but the pattern is general. LLMs have made it dramatically cheaper to produce plausible-looking ML papers. Conference workshops have not scaled their reviewer pools at the same rate. Admissions committees and hiring managers still treat "author on a NeurIPS paper" as a positive signal without distinguishing main track from workshop. The result is a market where paying for an author slot has measurable expected value for the student, the mentor, and the program operator — and a cost spread thinly across every reader who now has to do more verification work.
The ML subreddit response has been more useful than the original exposé. Several commenters pointed out that the structural fix is not to shame teenagers but to push venues toward stricter author-contribution statements, mandatory code release, reviewer compensation that matches the volume increase, and per-author submission caps. None of this is novel — biomedical journals have grappled with the same dynamics for two decades — but it has not yet propagated to ML venues at scale.
For working developers, the takeaway is narrower. Treat author lists and venue names as weak signals, not strong ones. Read code. Check whether the technique reproduces on your data. Be especially skeptical when the paper is recent, the venue is a workshop, the coauthor list is long, and the senior author's publication rate is implausible for one human in one year.
Originally published at pickuma.com. Subscribe to the RSS or follow @pickuma.bsky.social for new reviews.
Top comments (0)