Papers › Publishing Neural Networks in Drug Discovery Might Compromise Training Data Privacy

Publishing Neural Networks in Drug Discovery Might Compromise Training Data Privacy

22 Oct 2024arXiv:2410.16975archive 2025-07-28

Fabian P. Krüger, Johan Östman, Lewis Mervin, Igor V. Tetko, Ola Engkvist

This study investigates the risks of exposing confidential chemical structures when machine learning models trained on these structures are made publicly available. We use membership inference attacks, a common method to assess privacy that is largely unexplored in the context of drug discovery, to examine neural networks for molecular property prediction in a black-box setting. Our results reveal significant privacy risks across all evaluated datasets and neural network architectures. Combining multiple attacks increases these risks. Molecules from minority classes, often the most valuable in drug discovery, are particularly vulnerable. We also found that representing molecules as graphs and using message-passing neural networks may mitigate these risks. We provide a framework to assess privacy risks of classification models and molecular representations. Our findings highlight the need for careful consideration when sharing neural networks trained on proprietary chemical structures, informing organisations and researchers about the trade-offs between data confidentiality and model openness.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2410.16975")

Code

Syntology Ran 1 of 7 code samples harvested from 2 repositories linked to this paper; 6 have no recorded run. Of those that ran: 1 ran · our draft was wrong.

By repository: official repository: 7 samples from 2 repositories, 1 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

aidotse/leakpro officialmentioned in papermentioned on GitHubpytorchNOASSERTION report
fabiankruger/molprivacy officialmentioned in paperpytorch report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested; 1 ran; 0 honoured the contract we drafted; 6 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · our draft was wrong
6unverified

Licence: 6 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

setup_log fabiankruger/molprivacy/src/leakpro/__main__.py official repository ran · our draft was wrong MIT (permissive) · d794cf5be250c358 · report
cross_entropy_loss aidotse/leakpro/leakpro/attacks/utils/gan_losses.py official repository unverified licence not identified · pointer only · 40e19414623504e2 · report
get_meanstd aidotse/leakpro/leakpro/fl_utils/data_utils.py official repository unverified licence not identified · pointer only · 410c4f802ef3963a · report
get_used_tokens aidotse/leakpro/leakpro/fl_utils/data_utils.py official repository unverified licence not identified · pointer only · 4c7619cd6dc56029 · report
max_margin_loss aidotse/leakpro/leakpro/attacks/utils/gan_losses.py official repository unverified licence not identified · pointer only · 082f8511f888c815 · report
poincare_loss aidotse/leakpro/leakpro/attacks/utils/gan_losses.py official repository unverified licence not identified · pointer only · d97c476db8f72120 · report
singleton aidotse/leakpro/leakpro/attacks/utils/distillation_model_handler.py official repository unverified licence not identified · pointer only · 34ef863b49266b87 · report

Tasks

Drug DiscoveryMolecular Property PredictionProperty Prediction

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections