Package evidence
[email protected]
New Account With Lifecycle Hook: package first published 17 day(s) ago, 10 total version(s), has lifecycle hook
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
- 10
- First published
- May 2026
- Publisher
- podut
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
New Lifecycle Script Vs Previous: postinstall added in 1.3.3 vs 1.3.2: "node setup/postinstall.js"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (4 events)
- available → available · risk high · score 45 · status available -> available, risk high -> high, score 97 -> 45
- available → available · risk high · score 97 · status available -> available, risk high -> high, score 92 -> 97
- available → available · risk high · score 92 · status available -> available, risk high -> high, score 154 -> 92
- new → available · risk high · score 154 · status changed
Related candidates
Linked campaigns and clusters
podut
2 members · evidence strength 70Install-time lifecycle script — postinstall="node setup/postinstall.js"
2 members · evidence strength 70Install Lifecycle Remote Or Exec — postinstall="node setup/postinstall.js"
2 members · evidence strength 70Evidence
Static findings
2 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.3 vs 1.3.2: "node setup/postinstall.js" | 40 |
| medium | New Account With Lifecycle Hook | package.json | package first published 17 day(s) ago, 10 total version(s), has lifecycle hook | 10 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.3 vs 1.3.2: "node setup/postinstall.js" | 40 |
| medium | New Account With Lifecycle Hook | package.json | package first published 17 day(s) ago, 10 total version(s), has lifecycle hook | 10 |
| low | Install-time lifecycle script | package.json | postinstall="node setup/postinstall.js" | 5 |
Manifest
Package metadata
Scripts4
historynode setup/scan-history.jsinitnode setup/init.jspostinstallnode setup/postinstall.jsscannode hooks/pre-commit
Dependencies1
@modelcontextprotocol/sdk^1.12.0