PkgRadar

Package evidence

@ajna-inc/[email protected]

Credential file access: matched ".AWS"

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":["@ajna-inc/[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":["@ajna-inc/[email protected]"],"fail_on":"high"}'
Artifact bytes264,143
Previous version0.2.3
Published2026-05-20T23:54:06.162Z
SHA-25648fa135b237cb824ccef21497f7289d0e0406342aa30e0d3b074ed5b447e61a0

Why flagged

What the scanner saw

Credential file access: matched ".AWS"

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

Availability ledger

available

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

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

vinaysingh8866

3 members · evidence strength 65

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accesspackage/build/VaultsApi.jsmatched ".AWS"30