Home › Hard problems › Security

Security

Malicious packages in software supply chains

Solo: strongOne person can run a real test of this in about 8 weeks.

thousands of new packages arrive every dayone reviewercan't open them allnumpyrequestsreqeustspandaspopular-liba look-alike namea hijacked maintainerYour buildpip install reqeusts:one typo, and thebad one runs
Attackers publish look-alike packages and hijack real maintainers, and thousands of new packages a day is far more than people can review.

Why it is still open

Attackers publish look-alike packages and hijack maintainers. Thousands of packages ship daily, and review can't keep up.

An experiment one person can run in 8 weeks

Train a detector on known malicious npm or PyPI packages and test it on a month of new uploads.

Verdict: Solo: strong

Public data and a clear catch rate.

The solo test behind the verdict

  1. Can it be measured? There is a number that shows you did better, such as an error rate, a catch rate or a cost per answer.
  2. Is it cheap to try? It runs on a laptop, free open models and open data, or under about ₹50,000 of rented GPU time.
  3. Is there a public yardstick? A benchmark or dataset others use, so your result can be compared and believed.
  4. Would a small win get noticed? A lab, a funder or a customer would care about a 10% improvement, not only a full solution.

Four yeses means Solo: strong. Two or three means Solo: possible. Fewer means Follow, don't build.

PreviousMemory-unsafe code everywhereNextAI that finds vulnerabilities before attackers do

All 79 hard problems · Working on this, or know of a result we missed? basant@cleandataengineering.ai