npm PACKAGE

atmn 2.0.188

Warn

PkgFire would install this release with a warning.·Checked 1 hour ago·Published 30 October 2026

npmjs.com

Why

  • warnSuspicious behaviour

    Version 2.0.188 was published without npm provenance attestations, but the earlier version 2.0.172 had them. Losing provenance after previous versions carried it can indicate a publish made outside the normal CI-attested flow, as seen in the nx compromise.

  • warnSuspicious behaviour

    Possible credential in the published package: curl-auth-header

  • warnRelease cooldown

    Published 2 days ago, inside the 7-day cooldown. Most malicious releases are pulled within hours of publication, so a version this new has not yet had time to be caught.

  • warnProvenance lost

    This version was published without build provenance, but 2.0.172 was published with it. Provenance is produced by the repository's CI identity rather than by the token used to publish, so an attacker holding a stolen publishing token can release a version and cannot attest it. A maintainer who changed their release workflow produces the same pattern, so confirm which one this is before acting.

Provenance

A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.

Signature
Verified against the registry's key
Build provenance
None, though 2.0.172 had it

What the code does

On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.

Code reading

PkgFire's own reading of the files: what the code can do.

  • code-execdist/bin.js, src/actions/skills/skills.ts, src/cli.ts, src/config/loadConfig.ts, src/repo/findRepoRoot.ts
  • code-networkdist/bin.js, src/actions/api/callApi.ts, src/actions/env/fetchOrgInfo.ts, src/auth/createOrgApiKeys.ts, src/auth/keyless.ts

Source patterns

Patterns found in the source, including those malware is known to use.

  • capability-network-download
  • capability-network-lolbas
  • capability-network-outbound
  • capability-process-hooks
  • capability-process-spawn
  • provenance_regression
  • threat-filesystem-read
  • threat-runtime-environment-read

Other checked releases

Check every dependency before it installs

This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.

Start free How it works