SShortSingh.
Back to feed

Delhi Police arrest 22 over fake WhatsApp banking apps linked to 22,139 victims

0
·5 views

Delhi Police ran a five-day operation from 11 to 15 November across Jharkhand, Uttar Pradesh, West Bengal and Bihar, leading to 22 arrests, including suspected malware developers. The accused allegedly posed as bank staff and sent victims, mostly senior citizens, malicious APK files via WhatsApp under pretexts such as KYC updates or life certificate verification. Once installed, the apps reportedly harvested banking credentials, SMS messages and OTPs, enabling account takeovers and credit card misuse. Police linked the suspects to 11 cyber fraud groups, 2,080 NCRP complaints and proceeds exceeding Rs 20 crore, and reported a drop in APK fraud complaints in Delhi afterward, though they did not establish that the arrests caused it. Investigators are examining 63 phones, two laptops, two MacBooks and a tablet recovered during the raids.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Engineers Argue Knowledge of Codebases Must Move Beyond Individual Memory

A developer reflects on how engineering teams once relied on a few individuals who knew where key logic lived in large codebases. He notes that team processes such as documentation, review, pairing and tests were adopted to spread that knowledge more widely. With AI agents now writing most code, the team retains a broad picture of services and data flows, but the details have grown harder to track. He cites an engineer at Microsoft who argues that safeguards built against human error must now be applied to agent-generated code. The author agrees and suggests recording the reasoning behind code in tests, decision records and checks.

0
ProgrammingDEV Community ·

Developer Builds JavaScript Puppy Growth Predictor Using Breed-Based Maturity Coefficients

A DEV Community post describes how to build a puppy weight predictor that accounts for different breeds reaching adult size at different rates. The author argues that simple linear regression is inadequate and proposes a category-based model that assigns each size class its own maturity age. The approach adapts the common veterinary estimate of weight divided by age in weeks, multiplied by 52, and includes a damping factor for the final stage of growth. The article notes that predictions are most reliable between 12 and 25 weeks and that large-breed growth plates can remain open past week 70. It includes a TypeScript/JavaScript code example and links to a production version of the tool.

0
ProgrammingDEV Community ·

Yard Picking Pilot Overstated Gains; Relabelling Drove Most Error Reduction

A builders' merchant introduced a handheld scanning system for yard picking to reduce wrong deliveries, piloting it at its Harrogate branch from January to March. The pilot showed a drop in wrong items from 2.1% to under 0.7%, and the board approved company-wide rollout based on an expected reduction of about two-thirds. After a year, the company-wide error rate had fallen only from 2.4% to 1.7%, prompting questions about the gap. Analysis found that much of the pilot's improvement came from the manager's relabelling and reorganising of the yard, along with intensive on-site support and a quiet seasonal period. The company then applied the relabelling across all branches, bringing wrong items to about 1.1%, and revised its pilot methodology to use less favourable branches and longer testing periods.

0
ProgrammingDEV Community ·

Script compares Googlebot crawl logs per site section to spot post-deploy drops

A DEV Community guide explains how to detect which website sections Googlebot crawled less after a deployment. Instead of relying on Search Console's delayed sitewide graph, it uses raw access logs for a precise per-section view. The provided Python script filters Googlebot requests from Nginx or Apache logs, groups URLs by first path segment, and compares daily crawl counts and status codes before and after a cutoff time. Results are sorted by the largest crawl drops, with the status mix shown for each period. The article interprets patterns such as lower crawl rates from reduced internal links, rising redirects after URL changes, or new server errors that need investigation.