Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Versions published
- 1
- First published
- May 2026
- Publisher
- nhpkevte1576
- External confirmation
- MAL-2026-4823OSV match · pinned to high regardless of other signals
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["[email protected]"],"fail_on":"high"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Credential file access: matched "id_rsa"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
not present
Latest scanner note: [email protected] not present in registry metadata
Status history (5 events)
- available → not_present · risk none · score — · [email protected] not present in registry metadata
- available → available · risk high · score 10 · status available -> available, risk high -> high, score 52 -> 10
- available → available · risk high · score 52 · status available -> available, risk high -> high, score 102 -> 52
- available → available · risk high · score 102 · status available -> available, risk high -> high, score 52 -> 102
- new → available · risk high · score 52 · status changed
Related candidates
Linked campaigns and clusters
Js Hidden Powershell — hidden / non-interactive powershell invocation in package code — typically `-windowstyle hidden`, `irm | iex`, or `windowshide: true` — used to download-and-run payloads on windows installers.
10 members · evidence strength 90Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/payload.js | matched "id_rsa" | 5 |
| low | Install-time lifecycle script | package.json | postinstall="node utils.js" | 5 |
| low | Obfuscation Density | package/payload.js | high encoded/escaped-token density | 0 |
Manifest
Package metadata
Scripts4
buildtscpostinstallnode utils.jsprepublishOnlynpm run buildstartts-node index.ts
Dependencies10
@types/node^24.10.1@types/ws^8.5.12esbuild^0.27.4pino^9.3.2postinstall^0.11.2ts-node^10.9.2tsup^8.5.1typescript^5.9.3ws^8.18.0zod^3.23.8