Skip to main content

Shalabh D

Lead — Managed Security Services

Security Research · Penetration Testing · CTF · Bug Bounty · Web Security · Network Security

Shalabh leads Security Brigade's managed security services function, overseeing the processes behind continuous security monitoring, incident triage and customer follow-through. His focus is on turning security findings into clear, actionable next steps.

Articles by Shalabh D

Google Play reads your manifest, not your code path

Google Play's restricted-permission rules are written against what an app declares, not against what it calls. An app that never invokes an API can still carry the permission line in its merged manifest, because a library put it there. That is a store problem before it is a runtime one. The SMS and Call Log groups, QUERY_ALL_PACKAGES, and the eight permissions barred outright from personal loan apps, read off Google's own policy pages. Read 3 September 2026.

androidsecurity.in

Your Data safety form is a declaration about a binary, and the binary keeps changing

Google Play's Data safety form binds every developer with a published app. It covers data handled by third-party libraries and SDKs as well as your own code, and Google's position on who answers for it is one sentence long: you alone are responsible. That makes it one of the few store obligations you can actually check. A declaration and a merged manifest are two artefacts, and they can be read against each other. Read 3 September 2026.

androidsecurity.in

Every Play package must be registered by 30 September 2026 — and the install-side milestone is a different obligation

Two obligations, one date. Install-side verification enforcement begins on 30 September 2026 for users installing from seven named stores in Brazil, Indonesia, Singapore and Thailand, on certified devices running Android 7+. Separately, on the same date, all Play packages must be registered under Android developer verification, and Google's own word for the consequence is global removal from Google Play. Registration is decided on app signing key ownership and install share, so a rotated upload key, an agency-held key, or one package name shipping from two keys has to be resolved before the package can be registered. Every quotation checked 2 September 2026.

androidsecurity.in

Ransomware recovery: the paths out, in the order they are tried

Data comes back one of four ways: a backup restore that has actually been verified, a free decryptor for the family you are really dealing with, forensic recovery of what survives on the disk, and last, only as a last resort, the ransom. Each one turns on a fact about your environment you can establish before you commit to it, and none of them is worth doing until the estate is clean.

hacked.co.in

Which ransomware is this, and what the family name decides

You know you are encrypted. You do not yet know by what, and the questions that follow are all questions about the family: whether a free decryptor already exists for it, whether its operator publishes stolen data, whether the group appears on a sanctions list. Three things the payload left on your screen name it, two free services will read them for you, and none of it needs a vendor or a tool you do not have.

hacked.co.in

Business email compromise — the money left this morning

A payment went to an account that was not your supplier's. The instinct is to chase the money, and that is right. But a BEC is a mailbox intrusion first and a fraud second, and the two run on different clocks. What to do in the first hours, in what order, and why the mailbox investigation cannot wait for the recovery attempt.

hacked.co.in

How they got in — and why your logs decide whether you can answer

The morning after, the question is how. A short list of entry classes, each confirmed from a different record. Every one of those records is a log with a retention window set by whoever runs the infrastructure. Where that window is shorter than the intrusion, the honest finding is 'root cause undetermined', and this is how to write one.

hacked.co.in

Website defacement, or a Google warning on your site: the first hour

A replaced homepage, or a Chrome warning on your site. What to copy before you touch the server, and the CERT-In clause that puts a defaced site on a six-hour clock.

hacked.co.in

Preserve it before you rebuild

Powering the machine off, restoring from backup, re-imaging, and quietly cleaning up are four reasonable instincts, and each destroys something no technique recovers afterwards. What each one takes with it, and a preservation sequence a system owner can work through with what they already have, before anyone with a forensics kit arrives.

hacked.co.in

What moves the effort of a phishing simulation programme

Very little of the effort in a phishing simulation scales with headcount. The six drivers that actually move it, and how to place a programme in a small, medium or large band before asking for a proposal.

securityawareness.in

Why two quarters of click rates are not comparable

A click rate belongs to one population, one pretext and one moment. What has to be held constant between rounds, what changes quietly, and how to build an awareness series that supports a comparison.

securityawareness.in

Who may be in the target population of a phishing simulation

CERT-In's audit policy guidelines confine a phishing simulation's target population to agreed employee groups. SEBI directs regulated entities to extend training to outsourced staff. Both hold.

securityawareness.in

How a phishing simulation runs, and what you receive

A phishing simulation is a measurement exercise over a defined employee population: what is agreed before it runs, what the campaign does, and what the report and the debrief actually contain.

securityawareness.in

Cyber security awareness: what a programme can and cannot change

An awareness programme changes what an organisation does, not what any individual knows. What the RBI, SEBI and CERT-In instruments require, what a programme moves, and what it cannot.

securityawareness.in