PkgRadar

Package evidence

[email protected]

Remote Payload: matched "curl "

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
14
First published
May 2026
Publisher
jokerized

Recommended action

Block this update

Static 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"}'
Publisherjokerized
Artifact bytes417,446
Previous version0.2.12
Published2026-05-25T06:39:58.643Z
SHA-256db562a9ddffd787e3fb87d06c53c6639197834a564a9a3579af7fd539d8981f5

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.2.13 vs 0.2.12: "node scripts/postinstall.mjs"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

high
Last checked
highRisk
57Score
0.2.13Version
Status history (3 events)
  1. availableavailable · risk high · score 57 · status available -> available, risk high -> high, score 99 -> 57
  2. availableavailable · risk high · score 99 · status available -> available, risk high -> high, score 124 -> 99
  3. newavailable · risk high · score 124 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

jokerized

3 members · evidence strength 70

Evidence

Static findings

2 static · 1 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.2.13 vs 0.2.12: "node scripts/postinstall.mjs"40
mediumRemote Payloadpackage/run.shmatched "curl "12
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.2.13 vs 0.2.12: "node scripts/postinstall.mjs"40
mediumRemote Payloadpackage/run.shmatched "curl "12
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node scripts/postinstall.mjs"5

Manifest

Package metadata

Scripts7
  • doctornode scripts/doctor.mjs
  • mcpnode scripts/mcp-server.mjs
  • postinstallnode scripts/postinstall.mjs
  • setupnode scripts/install.mjs
  • startnode app-node/main.mjs
  • testnode --test app-node/*.test.mjs
  • vcnode scripts/cli.mjs
Dependencies5
  • @discordjs/opus^0.10.0
  • @discordjs/voice^0.19.2
  • discord.js^14.26.3
  • prism-media^1.3.5
  • wav^1.0.2