News for hackers. Stuff that matters.

A comment on Denial of service and source code exposure in React Server Components. Parent comment

Re:Denial of service and source code exposure in React Serve... by TZubiri on Thursday December 11, 2025 @06:56PM (#46239075)
I had this issue with a React app I inherited, there was a .env with credentials, and I couldn't figure out whether it was being read from the frontend or the backend.

So I ran a static analysis (grep) on the apk generated and

points light at face dramatically

the credentials were inside the frontend!

[ Parent | on HN ]
Re:Denial of service and source code exposure in React Serve... by jaredwiener on Thursday December 11, 2025 @08:05PM (#46239668)
Why would you have anything for the backend in an APK? Wouldnt that be an app, that by definition runs on the client?

Most frameworks also by default block ALL environment variables on the client side unless the name is preceded by something specific, like NEXT_PUBLIC_*

[ Parent | on HN ]
Re:Denial of service and source code exposure in React Serve... by mcpeepants on Thursday December 11, 2025 @09:54PM (#46240354)
> Most frameworks also by default block ALL environment variables on the client side

I’ve been out of full stack dev for ~5 years now, and this statement is breaking my brain

[ Parent | on HN ]
Re:Denial of service and source code exposure in React Serve... by TZubiri on Thursday December 11, 2025 @11:59PM (#46241015)
Why would you have anything for the backend in a browser app? Wouldn't that by definition run on the client?

These kind of node + Mobile apps typically use an embedded browser like electron or a builtin browser, it's not much different than a web app.

[ Parent | on HN ]