Summary
Togoder Security scanned the npm package detect-libc@2.1.2 on Oct 4, 2026. An AI review of 4 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
Spawning processes or shell commands
NPS-F9B47EFC56C3
The code uses childProcess.exec and childProcess.execSync to run 'getconf GNU_LIBC_VERSION 2>&1 || true; ldd --version 2>&1 || true' to determine the libc family and version. This is expected behavior for the detect-libc package, which is used to detect the C library on Linux systems. The command is hardcoded and does not take external input, so it is not a security concern.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| lib/detect-libc.js | safe | The code is safe; it only uses child_process to run a hardcoded command for libc detection, with no malicious patterns detected. |
| lib/elf.js | safe | The code is a benign ELF interpreter path parser with no malicious patterns detected. |
| lib/filesystem.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/process.js | safe | The code only reads process platform info and Node.js diagnostic reports locally without any network, process spawning, or file system access. |
Frequently asked questions
Is detect-libc safe to use?
Our AI source review of detect-libc@2.1.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does detect-libc contain malware?
No malware was identified in detect-libc@2.1.2 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was detect-libc checked?
Togoder Security downloaded the published npm package and had an AI model read its 4 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 detect-libc 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 detect-libc@2.1.2, cost nothing.