Package evidence
[email protected]
Install-time lifecycle script: postinstall="node scripts/postinstall-message.mjs"
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
- 28
- First published
- May 2026
- Publisher
- draeder
- External confirmation
- MAL-2026-4567OSV 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/postinstall-message.mjs"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (5 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 5 -> 3
- 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 42 -> 3
- new → available · risk high · score 42 · status changed
Related candidates
Linked campaigns and clusters
draeder
2 members · evidence strength 52Install-time lifecycle script — postinstall="node scripts/postinstall-message.mjs"
2 members · evidence strength 58Evidence
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/postinstall-message.mjs" | 5 |
Manifest
Package metadata
Scripts19
buildworker-build --releasecheckcargo check --target wasm32-unknown-unknownconfig:gennode scripts/generate-prod-config.mjsconfig:validatenode scripts/validate-config.mjsd1:init:localwrangler d1 execute freertc-signal --local --file scripts/d1-schema.sqld1:init:remotewrangler d1 execute freertc-signal --remote --file scripts/d1-schema.sqldeploywrangler deploy --env productiondeploy:local-prodnpm run config:validate && npm run config:gen && docker-compose -f docker-compose.prod.yml up -ddeploy:local-prod:logsdocker-compose -f docker-compose.prod.yml logs -fdeploy:local-prod:stopdocker-compose -f docker-compose.prod.yml downdeploy:rawwrangler deploydevnode scripts/non-cloudflare-server.mjsdev:cfnode scripts/dev-server.mjsdev:localnpm run dev:nodedev:nodenode scripts/non-cloudflare-server.mjsdev:prodnpm run config:validate && npm run config:gen && node scripts/prod-server.mjspostinstallnode scripts/postinstall-message.mjsprepacknode scripts/sync-worker-version.mjswizardnode scripts/wrangler-install-wizard.mjs
Dependencies1
ws^8.18.0