Navigating dual-use projects in biosecurity

Advice for the BlueDot biosecurity course and hackathons

Some projects designed to reduce biological risk can themselves be misused. This involves creating tools, datasets, or capabilities that bad actors could exploit.

Examples include:

• Building benchmarks to test whether AI models can assist with dangerous biology (the benchmark code or collated data could help malicious actors)

• Developing AI agents with access to biological tools

• Red-teaming exercises that probe biosecurity vulnerabilities

• Threat modelling that produces detailed attack scenarios

Even if you never release your results, releasing the methodology, the data, or the tools can be harmful in the wrong hands.

Dual-use is a spectrum, not a binary

Not all dual-use work is equal:

• Some should be done openly. Low-risk contributions to detection, broad-spectrum countermeasures, or policy analysis.

• Some should be done carefully. In controlled settings with experienced collaborators, perhaps with government stakeholder input.

• Some requires serious information security. Maybe even classification, with appropriate institutional backing.

It’s important to remember that your good intentions don’t eliminate the risk. Someone building a benchmark to measure misuse-relevant AI capabilities, even with the goal of demonstrating those capabilities should be restricted, is producing something that could itself be useful to bad actors.

What to do if you’re considering a project with dual-use dimensions

1. Get experienced mentors. This is the single most important step. Senior people in biosecurity have developed intuitions about what’s safe and what isn’t. They’ve seen projects go wrong. They have relationships with funders and policymakers who can help navigate tricky situations.

2. Don’t do it alone. The “unilateralist’s curse” applies here: if twenty-four people independently decide a risky project isn’t worth pursuing, but the twenty-fifth goes ahead anyway, the damage is done. Check your reasoning with others before acting.

3. Consider the institutional setting. Some work genuinely belongs in organisations with government relationships, security clearances, and established protocols for handling sensitive material.

4. Think about outputs. Before you create a dataset, tool, or benchmark, ask: if this were publicly released, who would benefit? If the answer includes potential bad actors, you need a plan for controlled access, or you need to reconsider whether this project should exist at all.

When in doubt

If you’re unsure whether a project idea has dual-use concerns, that uncertainty is itself informative. Reach out to your course facilitators, or to experienced biosecurity professionals who can help you navigate these questions.

The biosecurity field needs capable, ambitious people. But capability and ambition should be paired with caution and collaboration. The goal isn’t to discourage you from working on hard problems; it’s to ensure that when you do, the work makes things better rather than worse.