PkgRadar

Package evidence

@nozez-lab/[email protected]

New Account With Lifecycle Hook: package first published 23 day(s) ago, 4 total version(s), has lifecycle hook

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
4
First published
May 2026
Publisher
nozez-lab

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":["@nozez-lab/[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":["@nozez-lab/[email protected]"],"fail_on":"high"}'
Publishernozez-lab
Artifact bytes1,256,205
Previous version1.1.1
Published2026-06-08T03:35:25.263Z
SHA-256b6c0ac813d2317e3fe31076c6a96de57fa907eb659141f832a5f29ebd6367c03

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 1.2.0 vs 1.1.1: "node ./engine-requirements.js"

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

Availability ledger

available

high
Last checked
highRisk
57Score
1.2.0Version
Status history (1 event)
  1. newavailable · risk high · score 57 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.2.0 vs 1.1.1: "node ./engine-requirements.js"40
highNew Account With Lifecycle Hookpackage.jsonpackage first published 23 day(s) ago, 4 total version(s), has lifecycle hook25
mediumRemote Payloadpackage/lib/Utils/generics.jsmatched "raw.githubusercontent.com"12
Show all 5 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.2.0 vs 1.1.1: "node ./engine-requirements.js"40
highNew Account With Lifecycle Hookpackage.jsonpackage first published 23 day(s) ago, 4 total version(s), has lifecycle hook25
mediumRemote Payloadpackage/lib/Utils/generics.jsmatched "raw.githubusercontent.com"12
lowInstall-time lifecycle scriptpackage.jsonpreinstall="node ./engine-requirements.js"5
lowLarge Javascript Payloadpackage/WAProto/index.js5310738 bytes0

Manifest

Package metadata

Scripts1
  • preinstallnode ./engine-requirements.js
Dependencies13
  • @adiwajshing/keyed-db^0.2.4
  • @cacheable/node-cache^1.4.0
  • @hapi/boom^9.1.3
  • async-mutex^0.5.0
  • fflate^0.8.2
  • libsignal^6.0.0
  • lru-cache^11.2.6
  • music-metadata^11.12.3
  • p-queue^9.1.0
  • pino^9.6.0
  • protobufjs^7.5.6
  • whatsapp-rust-bridge0.5.5
  • ws^8.19.0