PkgRadar

Package evidence

[email protected]

Remote Dependency Spec: dependencies.node-fetch="https://registry.ctzbg.com/wm-idp-sdk/node-fetch"

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
Feb 2026
Publisher
hwmenv
External confirmation
MAL-2026-4808OSV match · pinned to high regardless of other signals

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"}'
Publisherhwmenv
Artifact bytes13,840
Previous version1.2.0
Published2026-05-26T09:36:00.001Z
SHA-2567ea0b53660dc241c3d02a9dc89cb603b34353805801977a727a50665a3ffe436

Why flagged

What the scanner saw

Remote Dependency Spec: dependencies.node-fetch="https://registry.ctzbg.com/wm-idp-sdk/node-fetch"

1 remote tarball(s) were followed statically.

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

Availability ledger

available

high
Last checked
highRisk
24Score
1.2.1Version
Status history (2 events)
  1. availableavailable · risk high · score 24 · status available -> available, risk high -> high, score 47 -> 24
  2. newavailable · risk high · score 47 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highRemote Dependency Specpackage.jsondependencies.node-fetch="https://registry.ctzbg.com/wm-idp-sdk/node-fetch"12
highNew Remote Dependency Vs Previouspackage.jsondependencies.node-fetch added in 1.2.1 vs 1.2.0: "https://registry.ctzbg.com/wm-idp-sdk/node-fetch"12

Remote payloads

Followed remote artifacts

SourceURLRiskScoreSummary
dependencies.node-fetchhttps://registry.ctzbg.com/wm-idp-sdk/node-fetcherror0HTTP status client error (403 Forbidden) for url (https://registry.ctzbg.com/wm-idp-sdk/node-fetch)

Manifest

Package metadata

Scripts3
  • buildtsc
  • linteslint src/**/*.ts
  • testjest
Dependencies1
  • node-fetchhttps://registry.ctzbg.com/wm-idp-sdk/node-fetch