PkgRadar

Package evidence

@kroniql/[email protected]

Credential file access, Obfuscation

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":["@kroniql/[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":["@kroniql/[email protected]"],"fail_on":"high"}'
Publishermoe.osaze
Artifact bytes34,553
Previous versionnone
Published2026-05-24T08:47:19.654Z
SHA-25689602395a85117cb432c8997065270f0f755bac1fa54307b839561425ba52205

Why flagged

What the scanner saw

Credential file access

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

scan error

status
Last checked
noneRisk
Score
0.2.0Version

Latest scanner note: HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/%40kroniql%2Fcli)

Status history (2 events)
  1. availablescan_error · risk none · score · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/%40kroniql%2Fcli)
  2. newavailable · risk high · score 33 · status changed

Related candidates

Linked campaigns and clusters

Repeated static TTPactive

Credential file access

124 members · evidence strength 86
Publisher / release actor burststale

Publisher burst: moe.osaze

3 members · evidence strength 60
Repeated static TTPcandidate

Credential file access

124 members · max score 80

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highCredential file accessmanifest30
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highCredential file accessmanifest30
lowObfuscationmanifest3

Manifest

Package metadata

Dependencies3
  • chalk^4.1.2
  • commander^12.1.0
  • prompts^2.4.2