Urgent.News

600+ sources. One page. See who else covered it.

Editions

AI

Open Discovery Challenge: How to Build a Verifiable Judge for AI-Designed Malaria Drugs

Open Discovery Challenge: How to Build a Verifiable Judge for AI-Designed Malaria Drugs Generative models can propose thousands of plausible molecules in a day. The harder question is no longer whether an AI can draw a molecule. It is whether anyone can tell if that molecule is potent, selective, safe enough to investigate, and possible to synthesize. That is the premise of the Open Discovery…

The Open Discovery Challenge aims to create a verifiable judge for AI-designed malaria drugs. The challenge focuses on a malaria parasite enzyme called PfDHODH. A successful drug must inhibit the parasite enzyme without affecting the human counterpart, survive in the environment, and cross cell membranes. The challenge provides a scoring system with six axes, including whole-cell activity, binding, selectivity, ADMET profile, novelty, and synthesis.

Validation of the scoring system revealed several issues, such as toxicity gate errors, size bias in molecular weight, and silent errors in novelty scoring. These defects highlight the difficulty of building a fair scientific judge for AI-generated molecules.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Why your AI coding agent should never see your API keys

Your AI coding agent needs your API keys. It needs them to call services, to test integrations, to run your stack. So you give it .env files, or you export keys into the environment, or you paste them…

  • API keys must remain secure when using AI coding agents
  • Developers often expose keys via .env files or environment exports
  • AI agents can leak secrets through context, output echo, and prompt injection