Summary
Togoder Security scanned the npm package aria-hidden@1.2.6 on Oct 6, 2026. An AI review of 3 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/es2015/index.js | safe | No malicious patterns detected; the code is a legitimate DOM accessibility utility for hiding or making inert sibling elements. |
| dist/es2019/index.js | safe | No malicious patterns detected; the code is a standard implementation of aria-hidden/inert accessibility utilities with no data exfiltration, credential harvesting, or dynamic code execution. |
| dist/es5/index.js | safe | No malicious patterns detected; the code is a legitimate implementation of aria-hidden/inert DOM accessibility utilities. |
Frequently asked questions
Is aria-hidden safe to use?
Our AI source review of aria-hidden@1.2.6 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does aria-hidden contain malware?
No malware was identified in aria-hidden@1.2.6 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was aria-hidden checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan aria-hidden together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in aria-hidden@1.2.6, cost nothing.