Mixed tick-borne infection complicates severe fever with thrombocytopenia syndrome in Korea
A Korean molecular study has found Rickettsia monacensis in a meaningful minority of patients with severe fever with thrombocytopenia syndrome (SFTS), a result that sharpens the diagnostic challenge around febrile tick-borne illness in East Asia. Among 129 patients with SFTS, nine were also positive for R. monacensis, yielding a co-infection prevalence of 7.9%. For clinicians facing a patient with fever, thrombocytopenia, and a recent tick exposure, that is not a trivial overlay; it is a reminder that a single pathogen can no longer be assumed to explain the entire syndrome.
SFTSV and R. monacensis share ecological space but not the same biology. The virus is transmitted by Haemaphysalis longicornis ticks, while R. monacensis is linked to Ixodes species. When two distinct tick-borne agents circulate in the same environment, a patient bitten during outdoor exposure can acquire one infection, the other, or both. Fever, cytopenias, and systemic inflammatory symptoms may look similar at the bedside, and that overlap can delay recognition of a second pathogen unless laboratory testing extends beyond the first positive result.
PCR and sequencing revealed dual pathogen signals
The investigators collected clinical samples from patients with SFTS and used one-step reverse-transcription PCR to identify SFTSV. Rickettsial nested PCR targeting the outer membrane protein A gene, ompA, was then used to search for R. monacensis, and phylogenetic analysis was performed to confirm species relationships. Seven of the sequences generated in the study clustered closely with R. monacensis on phylogenetic tree analysis, supporting the molecular identification.
The technical approach matters because it reduces the chance that a broad clinical syndrome is being overinterpreted on symptom pattern alone. Tick-borne illness often produces a compressed diagnostic window: by the time thrombocytopenia and transaminase abnormalities become obvious, the etiologic agent may still be unidentified. Nested PCR and sequencing can expose a second pathogen that routine clinical judgment would miss, especially when one infection dominates attention after initial testing.
The finding also raises a practical issue for treatment strategy. SFTS is viral, whereas rickettsial disease is bacterial and generally calls for different management. When both pathogens are present, the treatment path is no longer a matter of simply confirming a viral diagnosis and observing the natural course. A concurrent rickettsial infection can alter clinical urgency, diagnostic sequencing, and antimicrobial decisions.
Why co-infection can change bedside interpretation
SFTS is already a high-stakes diagnosis because it can produce severe systemic illness with thrombocytopenia, and clinicians in endemic regions are trained to think about it when a patient presents with an acute febrile syndrome after tick exposure. Rickettsial infection can add another inflammatory layer, making the clinical picture more difficult to interpret. Shared features such as fever and cytopenia are especially deceptive because they are not pathogen-specific; they reflect the host response to infection, not the organism itself.
Dual infection can also blur the meaning of severity. If a patient deteriorates after an SFTS diagnosis, clinicians may attribute worsening entirely to the viral syndrome. Yet a second tick-borne pathogen can contribute to persistent fever, inflammatory burden, or atypical evolution. In that setting, the signal is not simply academic. It affects whether the patient is managed as a mono-infection or as a mixed infectious process requiring broader consideration.
Seven phylogenetic matches strengthen the case for true infection
The phylogenetic clustering of seven sequences with R. monacensis strengthens the argument that the nested PCR signal was not random contamination or a nonspecific amplification artifact. Molecular confirmation is important in a study of this kind because tick-borne illness is often investigated in settings where multiple related organisms circulate together. Sequence-level support gives the prevalence figure more clinical weight than a PCR result alone would provide.
The prevalence estimate of 7.9% is large enough to change how endemic-area clinicians think about triage and testing. It does not mean every patient with SFTS should automatically receive the same expanded workup, but it does mean that a positive SFTSV result should not close the diagnostic process if the presentation is unusual, severe, or epidemiologically suspicious. A second pathogen can coexist with the first, and in tick-borne disease the exposure history often supports that possibility.
Diagnostic breadth is the main clinical takeaway
This study does not provide an endpoint in the conventional therapeutic sense, and it was not designed to measure mortality, hospital length of stay, or treatment response. Its value lies in diagnostic realism. In regions where multiple tick-borne pathogens circulate, fever with thrombocytopenia is a syndrome that demands molecular breadth, not a single-pathogen mindset.
The authors framed the findings as a call for differential diagnosis of tick-borne febrile illnesses, and the data support that position. The presence of R. monacensis alongside SFTSV suggests that clinicians may need to think in layers: the first layer identifies SFTS, while the second asks whether a bacterial co-infection is also present. If the second layer is missed, management may be incomplete even when the primary diagnosis is correct.
The study was supported by a research fund from Chosun University in 2024, and it represents one of the first molecular demonstrations that co-infection with R. monacensis occurs in a notable fraction of suspected SFTS cases in Korea. The remaining question is not whether mixed infection is possible; this dataset shows that it is. The more pressing question for endemic practice is how often it changes severity, treatment choice, and outcome in real patients, because those variables were not measured here.