Package evidence

@mirageshield/[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""

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: magicmisty

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":["@mirageshield/[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":["@mirageshield/[email protected]"],"fail_on":"high"}'

Publishermagicmisty

Artifact bytes40,815

Previous version0.1.1

Published2026-06-18T03:15:46.109Z

SHA-2566284132ab2c9eb496bc6aa054547d6470e0975c6589118684e63ec71196b26db

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.2 vs 0.1.1: "node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""

1 candidate cluster(s) currently reference this release.

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

Availability ledger

available

high

9h agoLast checked

highRisk

85Score

0.1.2Version

Status history (1 event)

new → available9h ago · risk high · score 85 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burstactive

magicmisty

2 members · evidence strength 64

Publisher / release actor burstcandidate

magicmisty

2 members · max score 85

Evidence

Static findings

4 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 0.1.2 vs 0.1.1: "node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""	30
high	New Account With Lifecycle Hook	package.json	package first published 0 day(s) ago, 2 total version(s), has lifecycle hook	25
medium	Suspicious Publish Context	manifest	{"package_age_days":0,"publisher":"magicmisty","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true}	10

Show all 5 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.2 vs 0.1.1: "node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""	30
high	New Account With Lifecycle Hook	package.json	package first published 0 day(s) ago, 2 total version(s), has lifecycle hook	25
medium	Suspicious Publish Context	manifest	{"package_age_days":0,"publisher":"magicmisty","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true}	10
low	Install-time lifecycle script	package.json	postinstall="node -e \"try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\\n [@mirageshield/mirage] Run \\x1b[1mnpx mirage\\x1b[0m to configure Mirage Shield\\n')}catch(e){}\""	5

Manifest

Package metadata

Scripts5

buildrm -rf dist && tsup
devtsup --watch
postinstallnode -e "try{require('fs').existsSync(require('path').join(process.cwd(),'package.json'))&&console.log('\n [@mirageshield/mirage] Run \x1b[1mnpx mirage\x1b[0m to configure Mirage Shield\n')}catch(e){}"
setupnode ./bin/init.mjs
testecho "no tests yet"