Package evidence
[email protected]
Install-time lifecycle script: postinstall="node scripts/post-install.js"
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
- 164
- First published
- Apr 2026
- Publisher
- quukk
- External confirmation
- MAL-2026-3757OSV 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
Install-time lifecycle script: postinstall="node scripts/post-install.js"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (6 events)
- available → available · risk high · score 5 · status available -> available, risk high -> high, score 3 -> 5
- available → available · risk high · score 3 · status available -> available, risk high -> high, score 24 -> 3
- available → available · risk high · score 24 · status available -> available, risk high -> high, score 59 -> 24
- available → available · risk high · score 59 · status available -> available, risk high -> high, score 35 -> 59
- available → available · risk high · score 35 · status available -> available, risk high -> high, score 24 -> 35
- new → available · risk high · score 24 · 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
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Install-time lifecycle script | package.json | postinstall="node scripts/post-install.js" | 5 |
Manifest
Package metadata
Scripts9
devnodemon cli.js --runinstall-servicenode scripts/install-silent.jspostinstallnode scripts/post-install.jspreuninstallnode scripts/pre-uninstall.jspublish:majornpm version major && npm publishpublish:minornpm version minor && npm publishpublish:patchnpm version patch && npm publishsyncnode scripts/sync-local.jsuninstall-servicenode scripts/uninstall.js
Dependencies6
@rongcloud/imlib-next^5.36.6axios^1.15.2fake-indexeddb^6.2.5jsdom^24.0.0node-windows^1.0.0-beta.8ws^8.16.0