Urgent.News

What's breaking now, across thousands of outlets.

Tech

Mahadev betting app promoter brought back from Oman, months after arrest in ₹6000 crore money laundering case

Sourabh Chandrakar set up the Mahadev betting empire along with co-founder Ravi Uppal.

Mahadev betting app promoter brought back from Oman, months after arrest in ₹6000 crore money laundering case

Sourabh Chandrakar, the alleged mastermind behind the Mahadev online betting syndicate, has been extradited from Oman to India after months in custody. The Central Bureau of Investigation (CBI) secured his extradition and he will be produced before the CBI Special Court in Raipur. Chandrakar, along with his associate Ravi Uppal, set up the Mahadev betting network in 2018, which reportedly generated illegal profits estimated at ₹6,000 crore.

The syndicate operated through a franchise-based network of betting panels and branches across India, using platforms like Tiger Exchange, Gold365, and Laser247.

Written by urgent.news from Hindustan Times's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 3 other outlets

Read the original at hindustantimes.com →

More in Tech

Building a Work-Hours Calculator? Time Arithmetic Is the Trap

If you have ever built a timesheet tool, a shift planner, or a payroll helper, you know the feature looks trivial until you write the first test.

  • Store times as minutes since midnight to avoid floating-point rounding errors
  • Perform calculations using integers, subtracting breaks before rounding, only round at end
  • Use modular arithmetic for overnight shifts, wrap time difference around 24-hour day

Antigravity and Codex security: stopping secret leaks with hooks and sandboxes

Originally published at ReclaimLLM . How Google Antigravity and OpenAI Codex agents read, print, and send secrets; what hooks and sandboxes cover; and where vendor docs leave failure modes…

  • Antigravity and Codex provide hooks for denying tool calls.
  • Sandboxes and approval boundaries restrict shell command capabilities.
  • Combine pre-tool hooks, network limits, and session capture for secret protection.

Which Sheet Automations Get a Human Approval Step, and Which Just Run?

Every Apps Script job we build for a small team ends with the same argument: should this run straight through, or should it stop and wait for a person? Our current line is roughly this: Runs straight through: reads, summaries, formatting, and anything that only writes inside the same spreadsheet and can be redone by running it again.

  • Jobs that modify data within spreadsheet can run automatically
  • Jobs deleting data, sending info outside company need human approval
  • Approval step creates idle time if approver unavailable

More from Sunday 1 November →