diff --git a/tools/varvamp/macros.xml b/tools/varvamp/macros.xml
index 658758b817b..9dae6805473 100644
--- a/tools/varvamp/macros.xml
+++ b/tools/varvamp/macros.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0"?>
 <macros>
-    <token name="@TOOL_VERSION@">1.1.1</token>
+    <token name="@TOOL_VERSION@">1.1.2</token>
     <token name="@VERSION_SUFFIX@">0</token>
     <xml name="main_parameters">
         <conditional name="main_params">
diff --git a/tools/varvamp/varvamp.xml b/tools/varvamp/varvamp.xml
index 4ba6007d41a..d0a77f2a63e 100644
--- a/tools/varvamp/varvamp.xml
+++ b/tools/varvamp/varvamp.xml
@@ -8,6 +8,8 @@
     </xrefs>
     <requirements>
         <requirement type="package" version="@TOOL_VERSION@">varvamp</requirement>
+        <requirement type="package" version="2.0.1">primer3-py</requirement>
+        <requirement type="package" version="0.7.17">seqfold</requirement>
     </requirements>
     <version_command>varvamp --version</version_command>
     <command detect_errors="exit_code"><![CDATA[
@@ -458,6 +460,6 @@ Testing with a new alignment/analysis:
 As a first check whether a new alignment of viral sequences can be used with specific settings of the tool, it may help to disable all configurable outputs, which will leave you with only the Analysis Log. This will be enough to see if there are any errors with the combination of alignment and settings, and whether you are on a roughly correct track (varVAMP reports some primers, for example). This way, you're not flooding your analysis history with lots of likely useless datasets, and once you've fixed potential issues you can add back more outputs and rerun the analysis.
     ]]></help>
     <citations>
-        <citation type="doi">https://github.com/jonas-fuchs/varVAMP/</citation>
+        <citation type="doi">10.5281/zenodo.10908223</citation>
     </citations>
 </tool>