Package evidence

[email protected]

Install-time lifecycle script: install="node 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: 6
First published: May 2026
Publisher: thermonuclear

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.

Inspect tarball Add to CI gate

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"}'

Publisherthermonuclear

Artifact bytes1,556

Previous version1.3.0

Published2026-05-30T12:54:20.311Z

SHA-25675c628e61e7e873cc982c28453a95ec6f192ed44bfbfc158f9af3cd561aa0778

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: install added in 1.3.1 vs 1.3.0: "node install.js"

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

Availability ledger

not present

status

4d agoLast checked

noneRisk

—Score

1.3.1Version

Latest scanner note: [email protected] not present in registry metadata

Status history (2 events)

available → not_present14d ago · risk none · score — · [email protected] not present in registry metadata
new → available18d ago · risk high · score 45 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	install added in 1.3.1 vs 1.3.0: "node install.js"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	install added in 1.3.1 vs 1.3.0: "node install.js"	40
low	Install-time lifecycle script	package.json	install="node install.js"	5

Manifest

Package metadata

Scripts1

installnode install.js