Nishant Kumar

Adventurous, Optimistic, Love , Peace✌

DB ORA:ORA

[Nishant Kumar @nish_cool]

@austinnotduncan hey guys, this is Nishant.
I was wondering for a long time, the background is real?
I see the same in @JayzTwoCents videos🤓

[Nishant Kumar @nish_cool]

@IndianGems_ Biggest joke of the millennium 🤣🤣🤣🤣🤣
This guy is busy making fortune for his sons and we fool are working hard for it.
This babu alleged murdered a young girl and got away with it. Karma will return for sure.

[Nishant Kumar @nish_cool]

@dealztrendz Looted , thanks @dealztrendz
Those who are curious , it is 2nd gen 😁

[Nishant Kumar @nish_cool]

@dealztrendz And don’t forget the headache it will bring to automobiles. We are already struggling with E20 with drop in mileage power and efficiency but our govt is busy creating fortune for their kin.

[Nishant Kumar @nish_cool]

@IndianOilcl Make it 100% and make your bootlicking minister happy. Do hell with public who already suffered with E20 scam.

[Nishant Kumar @nish_cool]

@narendramodi Just like Ganges river , just like Yamuna river 🙏🏻

[Nishant Kumar @nish_cool]

@PMOIndia Is this the developed nation we dreamt of ? What happened to the chest thumping vishwaguru ? Fire bridge arrived after 45minutes , is this what you call immediate relief response ?

[Nishant Kumar @nish_cool]

@Saurabh_MLAgk Vishwaguru for a reason

[Nishant Kumar @nish_cool]

@dealztrendz Received! Isse jyada de hi nahi rahe the 😶
Give few to Delievery guy.
Thanks @dealztrendz

[Manish Sharma @Cheekytogeeky]

be @ni5arga

→ 19 years old, from West Bengal, studied in Delhi for a few years
→ just finished his own Class 12 exams in 2026
→ calls himself a hobbyist cybersecurity researcher
→ says he is an engineer, not a hacker
→ built an OSINT engine, a stock-tracking TUI, a pastebin in Rust
→ once found bugs in FOSS United and disclosed them quietly
→ just another CBSE student watching his own board roll out a new digital marking system

then he opened the portal

→ CBSE moves Class 12 evaluation to On-Screen Marking, 1.8 million students affected
→ Nisarga sees the portal link is fully public, gets curious
→ opens DevTools, downloads the Angular JavaScript bundle
→ first vulnerability found in 30 minutes
→ a literal master password sitting in plain text inside the frontend code
→ enter it, the OTP field auto-fills, the entire login flow gets bypassed
→ OTP validation happens in the user's browser, not on the server
→ no route guards, every internal page reachable by editing browser storage
→ password reset API never checks the old password
→ systemic IDOR across the entire API, change one value in sessionStorage, become any examiner
→ outcome: take over any teacher account, view answer sheets, edit marks

25 February 2026. He reports everything to CERT-In the same day.

→ CERT-In asks for a screen recording, he sends a full walkthrough
→ acknowledgement comes back as a boilerplate reply
→ reference number assigned: CERTIn-16590126
→ he follows up multiple times. no response.
→ three months pass. portal still live. Class 12 results released. vulnerabilities still there.
→ 22 May: publishes the blog post and a thread on X
→ Deedy Das, Satish Acharya, Internet Freedom Foundation amplify it
→ the post goes viral
→ CBSE issues a clarification: that was just a test portal, no breach
→ the URL CBSE cited in their own tweet was not even a registered domain
→ a friend buys the domain and points it at Nisarga's blog
→ CBSE quietly deletes the tweet

then it gets worse

→ 25 May: finds an SQL injection vulnerability on the live production portal
→ reports to CERT-In, gets a one-line thank you
→ gains admin access to the live https://t.co/1WpmNGsczK server
→ portal stays up for four more hours
→ he uploads anime videos and memes, links them publicly from CBSE servers
→ plays a viral Japanese song on a CBSE page, makes the news for it
→ CBSE finally takes the whole portal down

then he reads the database

→ master table accessed: 10 GB, 9.3 million records
→ examiner names, addresses, school names, bank account details
→ passwords stored in plain text
→ login tokens anyone can paste into a browser to log in as that user
→ 31 May: finds a second live CBSE production portal, 45,074 records of failed payments
→ emails, phone numbers, payment IDs, order IDs, all readable
→ 31 May, the bigger one: an AWS S3 bucket is misconfigured
→ ListObjectsV2 works without authentication, the bucket root is listable
→ samples pulled from 18 lakh scanned 2026 answer sheets, every subject
→ multiple institutions sharing the same bucket
→ also notices something strange in the scans: bedsheets visible in the background of answer sheets CBSE paid for proper scanners to handle

CBSE responds

→ posts an AI-generated image saying the system is robust and secure
→ three days later admits some vulnerabilities existed and have been contained
→ refuses to name the cybersecurity firm doing the audit
→ claims they tried contacting him. he says they have not.

→ Internet Freedom Foundation writes to the Ministry of Education and CERT-In
→ asks for an investigation into CBSE, a review of the contract with vendor Coempt EduTeck, a full audit

→ he points out he could have sold this data and made a lot of money
→ he did not. he is a CBSE student too.
→ his own analogy: the door wasn't just unlocked. the key was lying on the ground in front of everyone.

a 19-year-old with a anima pff broke a national exam evaluation system in 30 minutes with browser developer tools and the government is still pretending it was a test environment

[Nishant Kumar @nish_cool]

@cbseindia29 You bring nothing but disgrace to our country. Corruption has spoilt you and you are doing the same with the future of our country.

[Dev @refocus21]

Meet Vedant Shrivastava, Nisarga Adhikary, and Sarthak Sidhant ,they exposed CBSE in every possible way :

17 years old Vedant Shrivastava :

> Applied for the CBSE re-evaluation process
> Got a different Physics answer sheet
> Posted it on X
> Got labelled "Pakistani" by the BJP IT cell
> Brought CBSE to its knees and proved them wrong

19 years old Nisarga Adhikary :

> Bro hacked the CBSE website
> Reported the vulnerability to them
> But they didn't take any action
> Then bro posted it on X
> Showed everyone that it could be hacked

18 years old Sarthak Sidhant :

> Bro exposed a CBSE tender
> Took it to X
> Wrote a detailed thread
> Explained how the CBSE OSM tender conditions allegedly favoured COEMPT
> And today came on the media
> Exposed them with facts

These three boys are doing what whole media failed to do, all of them took x to expose CBSE .

[Malay Krishna @Malay4Product]

This is an unbelievable piece of work by Sarthak and something that requires amplification.

Let me explain what he found, in simple terms.

Sarthak is a Class 12 student from the 2025-26 batch, one of the 17 lakh students whose answer sheets went through CBSE's new On-Screen Marking system.

He spent days reading through CBSE's evaluation tenders, scraped all 576 tenders CBSE has issued, and tracked how the rules changed across three versions of the same tender.

The core finding is that the company that won the contract to scan and grade 17 lakh students' answer sheets is Coempt Eduteck.

Coempt used to be called Globarena Technologies. Globarena was the company behind the 2019 Telangana intermediate exam disaster, where software failures led to 3.8 lakh students getting wrong or missing marks, and 23 students died by suicide.

A government committee found systemic failure and negligence. Six months later, Globarena rebranded to Coempt Eduteck.

So a company with that track record won a contract to handle 17 lakh CBSE students. Sarthak's investigation is about how the rules were rewritten to let that happen.

The tender was issued three times.

> First tender, February 2025. It existed, then disappeared from the public GeM portal. Sarthak scraped all 576 CBSE tenders and this one was missing from the archive entirely.

> Second tender, May 2025. Four companies applied including TCS and Coempt. All four failed the technical evaluation. Cancelled.

> Third tender, August 2025. Coempt won. Between the second and third tender, a series of rule changes happened, and every single one made it easier for Coempt to qualify.

Here is what changed, one by one.

01. The old rules disqualified any company with a history of abandoning work, failing to complete contracts, or financial weakness. The new rules deleted this clause entirely. Coempt's Telangana history stopped being a barrier.

02. The old rules disqualified any company that was "blacklisted earlier." The new rules changed this to "currently blacklisted." Because Globarena rebranded after Telangana, removing the word "earlier" effectively erased their past.

03. The rules required Rs 50 crore average turnover over three years. Coempt's exact average came to Rs 50.86 crore. They cleared the bar by less than 1%. Earlier, a smaller company had asked CBSE to lower the bar to Rs 30 crore for fairer competition. CBSE refused. So the bar was kept high enough to block small players, but sat exactly low enough for Coempt to scrape through.

04. Software maturity is measured on the CMMI scale, 1 to 5. The old rules required Level 5. The new rules dropped it to Level 3. Coempt is a Level 3 company.

05. The cooling-off period for engaging retired CBSE officials was cut from two years to one. This makes it easier to use recently retired insiders to influence the process.

06. The old rules required experience with large projects of at least 5 lakh students each. The new rules removed the student count and counted cumulative answer-book volume across small projects instead. Coempt has many small fragmented university contracts. This helped Coempt and hurt TCS.

07. The old rules required bidders to own their own data centre and disaster recovery centre on Indian soil. The new rules allowed third-party MeitY-empanelled cloud hosting. Coempt runs on AWS and Azure. This helped Coempt and hurt TCS, which owns its own data centres. It also means student data is no longer on sovereign, Indian infrastructure.

08. The old rules required the bidder to own or control the complete source code of its software. The new rules deleted this. Coempt's platform runs on Microsoft's proprietary IIS, which they don't own.

09. A last-minute corrigendum, issued right before bid submission, removed CBSE's own power to blacklist the firm if its software failed catastrophically. So even a Telangana-scale failure couldn't get Coempt banned from future government tenders.

10. The penalty structure shifted from punishing mistakes to punishing delays. The old rules fined the vendor for wrong scanning, merged pages, and unscanned books. The new rules dropped those and instead levied Rs 50,000 per day for delays. This incentivises rushed scanning over accurate scanning.

11. The old rules had a hard accuracy threshold, error rate not to exceed 0.5%. The new rules removed this number entirely.

12. The old rules specified proper book and robotics scanners. The new rules just say "sufficient scanners." The definition was vague enough that, as Sarthak notes, the scanning could be done with a phone on a stand.

13. On the security side, the contract required a VAPT (vulnerability and penetration test) certified by CERT-In before go-live, and a restricted beta phase before launch. The system clearly wasn't restricted, because the other researcher, Nisarga, was able to access it and find vulnerabilities four days before go-live. So the mandatory security audit appears to have been bypassed.

These are more than a dozen rule changes, all between the failed tender and the winning tender, all pushing in the same direction, all benefiting the one company with the worst track record in the field.

The security holes Nisarga found last week now have an explanation. The system was built by a vendor that was specifically allowed to skip the security certification, the source code ownership, the data sovereignty, and the quality thresholds the original rules demanded.

Following things need to happen immediately;

1. An immediate CAG audit of the tender process.
2. A parliamentary debate on the topic.
3. An independent investigation into
> Why the first tender vanished?
> Why the disqualification clauses were deleted?
> Why the turnover bar was held exactly where it was?
> Why the security level was dropped?
> Why the blacklisting power was removed at the last moment?

Sarthak, this is genuinely exceptional investigative work. Far better than most journalists with full resources ever manage. Take a bow. :)

[Gulshan Pahuja @GulshanPahujaJR]

"People ask me, why I don’t file a PIL.
With nearly 4,000 pending,
why would anyone smart (judges) hang a bell around their neck?
Audio-Video court recording will only happen if the PUBLIC OVERWHELMINGLY demands it.

[Gurpreet Garry Walia @garrywalia_]

धर्मेंद्र प्रधान का इस्तीफ़ा होना चाहिए रीट्वीट अगर सहमत है .

[Cockroach is Back @Cockroachisback]

Dharmendra Pradhan must resign!

[Cockroach Janta Party @CJP_2029]

Education Minister of India must resign! Students are committing suicide because of NEET paper leak.

Cockroaches, take this forward. We need to fix the accountability.

[Nishant Kumar @nish_cool]

@ImWisely_ @dealztrendz You forgot 3% gst and what about making charge ? Nobody gonna give you pure gold as is.

[Nishant Kumar @nish_cool]

@dealztrendz Can we top up our membership on existing membership by purchasing this ?

[Nishant Kumar @nish_cool]

@volklub Lol 😂

[Nishant Kumar @nish_cool]

@DeepikaBhardwaj Use quikcompare app , it will prices from all quick commerce app and then directly order from it. It is very convenient ensuring you get best deal 😁