Mahipal Maderna Bhanwari Devi Scandal Video: |top|

The video, however, was not just a political weapon; it was a death sentence. The CBI investigation revealed that Maderna suspected Bhanwari of leaking the CD to the media, and he decided to eliminate her. He hired two criminal gangs to abduct and murder her. Malkhan Singh also colluded in the plot, fearing Bhanwari would publicly reveal him as the father of her child.

When the blackmail escalated and the threats to release the video became severe, a conspiracy was allegedly hatched to eliminate her. The Disappearance and Murder Investigation

The scandal began when Bhanwari Devi's husband, Ram Lal, a BJP worker, accused Mahipal Maderna of having an affair with his wife. Ram Lal alleged that Maderna had been harassing his wife and had even offered him a bribe to keep quiet about the matter.

In 2005, Maderna was convicted of adultery and sentenced to two years in prison. He was also fined and forced to resign from his position as Minister for Water Resources. mahipal maderna bhanwari devi scandal video

The Mahipal Maderna Bhanwari Devi scandal, a sordid tale of sex, power, and corruption, has left an indelible mark on the politics of Rajasthan, India. The scandal, which came to light in 2005, involves Mahipal Maderna, a former Minister for Water Resources in the Rajasthan government, and Bhanwari Devi, a woman who was allegedly coerced into a compromising situation with Maderna.

Bhanwari Devi, on the other hand, was a woman from a humble background who worked as a junior engineer in the Water Resources Department. Her life took a dramatic turn when she was allegedly coerced into a relationship with Mahipal Maderna.

The scandal led to a re-evaluation of the state's policies on corruption and harassment. The Rajasthan government implemented new measures to prevent corruption and ensure greater accountability in the workplace. The video, however, was not just a political

According to the CBI, Bhanwari had an illicit relationship with Malkhan Singh Bishnoi, who was later confirmed to be the biological father of her youngest daughter. She was also introduced to Mahipal Maderna through Malkhan Singh and soon developed a similar relationship with him. It was her relationship with these two powerful men that would ultimately prove fatal.

The Bhanwari Devi case stands as a stark example of how power, sex, and blackmail can lead to a brutal murder and a protracted political crisis. The video that brought the scandal to light was not just evidence; it was the instrument of blackmail that triggered the chain of events. The legal process, now without its prime accused, serves as a cautionary tale about the nature of justice, the fallibility of the powerful, and the tragic ending for a woman who sought to use a scandal to change her circumstances. Despite a thorough investigation by the CBI, the decade-long wait for a final verdict remains a grim reminder of the complexities of India's criminal justice system.

If you want, I can:

The scandal had severe repercussions for the Rajasthan Congress government:

On , Bhanwari Devi went missing. Her husband, Amarchand, filed a habeas corpus petition in the Rajasthan High Court, alleging that she had been abducted at the behest of Minister Mahipal Maderna and his associates. The state government, under increasing pressure, finally handed over the investigation to the Central Bureau of Investigation (CBI) on September 14. Maderna was eventually sacked from the cabinet on October 16 after he refused to resign.


1. E.g. XSD schemas and validation mechanisms.
2. Examples of contracts above the threshold would be: (a) public works contracts which value is above EUR 5 186 000; (b) public supply and service contracts which value is above EUR 134 000 awarded by central government authorities; (c) public supply and service contracts which value is above EUR 207 000 awarded by sub-central contracting authorities; (d) EUR 750 000 for public service contracts for social and other specific services listed in Annex XIV. For more details, see Article 4 (where the threshold are established), Article 5 (about special cases associated to Lots), and Annexes III and XIV of the Directive 2014/24/EU.
3. http://www.cenbii.eu/
4. http://www.esens.eu/
5. E.g. the Commission’s e-Procurement platform, e.Prior, is using UBL-2.1; The ISA Program (namely Action 1.1, about semantics) is recommending UBL and implementing the Core Vocabularies defined in ISA based on UBL-2.1; Pilots and developments, both trans-European and national, are using UBL-2.1 libraries and/or Naming and Design Rules (e.g. The large Scale Pilot PEPPOL and Open PEPPOL; BRIS, the Business Registers Interconnection System; OIOUBL, in Denmark and Northern Europe, for the e-Invoice; CODICE, the Spanish specification for e-Procurement; etc.).
6. In the ESPD-EDM, the Contracting Authority is represented by "Contracting Party", the generic term representing a Contracting Body, Authority or Entity.
7. this UML was produced using the MS-Visio tool, thus the double semicolon "::" after the prefix. The XML syntax only uses one semicolon ":".
8. see the CCV-CommonAggregateComponents-1.0.xsd library for its XML definition
9. Source: CEN/BII-WS3
10. Source: CEN/BII-WS3
11. Source: UBL (look into the Common Aggregate Component library of the xsd folder inside the UBL-2.1 distribution package)
12. The ESPD Service confirms the presence of an element that in the schema is optional using the ISO Schematron validation method. The reason why the cardinality of the XSD schema is kept optional for most of the elements is to provide a model that is flexible enough so as to be used in other contexts different to the ESPD Service, e.g. for procurement projects at national or subnational levels where the value of the contracts are below the threshold; or for its use in systems where the ID of the instantiated objects is considered enough to identify a Criterion or a Requirement. For details about Schematron see http://www.schematron.com/spec.html.
13. In the XML this is the attribute GROUP_FULFILLED.ON_TRUE of the element RequirementGroup
14. This notation CRITERION.EXCLUSION.CONVICTION.* is to be read as ''it applies to all the selection criteria, which are part of the exclusion criteria group''. See the criteria tables for the complete taxonomy of criteria and each criterion code label.
15. For the time being e-Certis only contains Criteria.
16. http://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32009D0316
17. See [DOC-REF-8] for the complete taxonomy of criteria and each criterion code label.
18. Thus, the ESPD Service will use the answer to show it in the User Interface and to include it in an XML instance.
19. i.e. a couple of values corresponding to amount and year.