Dinotefuran can present a high risk to bees when exposure occurs, because it is a systemic neonicotinoid with strong intrinsic toxicity to pollinators. Whether that hazard becomes real-world damage depends on the exposure scenario—especially contact with treated flowering resources or dietary intake via contaminated pollen/nectar. This article focuses on decision-grade information (mechanism, exposure, persistence, regulatory lens, and a buyer checklist). Always follow the product label and local regulations.
| Decision context | Likely bee exposure route | Risk signal | What you should verify (buyer lens) |
|---|---|---|---|
| Uses that can contaminate flowering resources | Dietary (pollen/nectar) + contact | Highest concern | Local label restrictions; pollinator statements; residue data expectations |
| Ornamental/urban landscaping near forage | Direct + dietary | High incident sensitivity | Use pattern suitability; applicator controls; incident history awareness |
| Non-flowering / enclosed / indoor use patterns | Minimal foraging exposure | Lower concern | Confirm that the approved use pattern truly limits environmental exposure |
| Markets with tight neonicotinoid scrutiny | Compliance/registration gating | High regulatory risk | Registration status; permitted crops/sites; packaging/label language readiness |
This is the core framing regulators use: Risk = Hazard × Exposure—high hazard alone does not predict outcomes without a clear exposure pathway.
Dinotefuran is a neonicotinoid (Group 4A) systemic insecticide used against a wide range of sap-feeding pests. For bee safety, “systemic” is the key word: a systemic active ingredient can move within plant tissues, which can create dietary exposure if residues reach pollen and nectar.
Risk conversations around neonicotinoids are usually less about “does it kill insects” and more about whether foraging pollinators can be exposed through normal feeding. EPA’s bee risk assessment framework explicitly distinguishes foliar contact exposure from seed/soil systemic exposure pathways and evaluates pollen/nectar residues as a major route.
Dinotefuran acts on the insect nervous system by targeting nicotinic acetylcholine receptors (nAChRs). At a high level, this disrupts normal nerve signaling and can lead to paralysis and death in susceptible insects.
From a portfolio and compliance perspective, MOA affects:
Resistance management expectations in the target pests (rotation planning)
Non-target risk profiles (pollinators are insects, so receptor-level sensitivity is plausible)
Label language and mitigation requirements tied to pollinator protection
EPA and peer-reviewed mechanistic work both position dinotefuran within neonicotinoid neuroactive chemistry, even noting it may interact with nAChR subtypes in ways that differ from other neonics.
Conclusion first: Dinotefuran shows very high acute toxicity to honey bees in standard laboratory endpoints, and regulators also evaluate longer-term (chronic/sublethal) effects and colony-level outcomes where exposure is plausible.
In EPA’s pollinator risk materials referenced in the dinotefuran regulatory decision documents, the adult honey bee acute oral LD50 is reported in the microgram-per-bee range, which places dinotefuran among the more acutely toxic insecticides to bees when exposure occurs.
Procurement teams often focus on “does it cause mortality,” but regulators increasingly look at repeat exposure and colony relevance—because reduced foraging efficiency, impaired thermoregulation, or altered behavior can translate into colony stress even without dramatic kill events. EPA’s tiered approach explicitly escalates from individual-bee toxicity screens to measured exposure and colony-level studies when risk flags appear.
Conclusion first: Bee exposure is driven by contact (overspray/drift/residues on surfaces) and dietary intake (contaminated nectar/pollen). Systemic use patterns raise the probability of dietary exposure in relevant crops or ornamental plants.
Contact with treated plant surfaces or drift onto flowering vegetation
Residues remaining toxic on foliage for a period after treatment (a standard assessment endpoint)
Research on systemic applications in woody landscape plants has documented dinotefuran residues in nectar in the season of treatment, supporting the plausibility of dietary exposure where pollinators forage.
A well-documented case study from Wilsonville, Oregon reported large-scale bumble bee mortality associated with dinotefuran exposure on flowering ornamental trees, underscoring that exposure in suburban/commercial landscapes can be consequential when it intersects with active foraging.
Conclusion first: Dinotefuran persistence is variable and depends on matrix and conditions (soil, water, sunlight, microbial activity). For bee risk, what matters is not a single “half-life number,” but whether residues can remain available during foraging windows.
EPA’s fact sheet describes dinotefuran as highly water-soluble with low soil adsorption potential (mobility), and reports dissipation behavior that can extend across weeks to months depending on conditions (for example, soil metabolism timeframes and relatively rapid photolysis in water). These characteristics matter because they influence where residues can move and how long they may remain environmentally relevant.
For compliance planning, you should treat “persistence” as a scenario question:
Could residues be present in flowering resources during foraging?
Does the use pattern create repeat exposure risk?
Are there local constraints around sensitive habitats and pollinator protection?
Conclusion first: Regulators generally manage pollinator risk through a combination of risk assessment (hazard + exposure) and label controls, with special attention to contact exposure and dietary exposure from pollen/nectar.
EPA describes a tiered process: conservative screening first, then refinement using measured exposure (including residues in pollen/nectar) and colony-level evidence when needed.
In parallel, EFSA’s updated bee guidance emphasizes structured assessment for honey bees, bumble bees, and solitary bees, reflecting broader pollinator coverage in risk evaluation.
EPA has published updated actions and labeling approaches for pollinator protection, including neonicotinoid label updates intended to reduce exposure risk. For buyers, that translates into a practical truth: your label language and approved uses are part of the product—not an afterthought.
The European Commission notes major regulatory actions restricting certain neonicotinoids due to bee risk concerns, which shapes risk perception and compliance expectations even in markets where dinotefuran remains available.
A credible supplier can answer, in writing:
Which exposure pathways are relevant for the intended market use pattern
What the label actually allows (and does not allow)
Which support files are available for registration/import due diligence
Yes—dinotefuran shows very high intrinsic toxicity to bees in standard test endpoints, and regulators treat it as a pollinator-relevant active ingredient. Real-world risk depends on exposure (contact and dietary routes).
Systemic insecticides can create dietary exposure when residues reach nectar/pollen. Field research in landscape settings has detected dinotefuran residues in nectar following treatment, supporting the plausibility of this pathway where bees forage.
Because exposure can be intense where treated flowering ornamentals overlap with active foraging. A published case study linked dinotefuran exposure to a large bumble bee mortality event in a suburban commercial landscape.
They use tiered risk assessment: conservative screening plus refined exposure and colony-level evidence when necessary, then manage risk through label conditions and mitigation measures.
Not necessarily. Hazard is only one side of the equation. Without exposure—especially via flowering resources—field risk can be much lower. That is why labels and approved use patterns matter.
If you are assessing dinotefuran for a regulated market, request a spec & compliance pack first: label language set, SDS/TDS/COA template, and registration-ready documentation aligned to your target use pattern.