StepSecurity Adds Package-Configuration Auditing to Dev Machine Guard

· Original article ↗

Summary

StepSecurity announced Package Configs, a Dev Machine Guard feature that audits developer machines’ package registries, cooldown settings and credential exposure to help identify gaps exploited by npm and PyPI supply-chain attacks.

Key points

  • Package Configs inventories npm, pnpm, bun, yarn and pip configuration files across global, user and project scopes on developer machines.
  • It reports each device’s effective package registry and the configuration source, helping identify machines that fetch directly from public registries rather than an internal registry or gateway.
  • The feature flags missing or unsupported cooldown settings, including cases where a package-manager version must be upgraded.
  • It identifies registry credentials hardcoded in configuration files versus credentials referenced through environment variables.
  • StepSecurity describes cooldown and controlled internal registries as defenses against freshly published malicious package versions.
  • The feature is part of Dev Machine Guard, uses its existing agent, and is described as supporting macOS, Windows and Linux.

Article Details

Event Type
Security product feature announcement
Impact
StepSecurity announced Package Configs for Dev Machine Guard, available in the dashboard for existing users. It audits package-manager configuration across developer machines to identify registry-routing gaps, missing or unsupported cooldown policies, and hardcoded registry credentials. The feature is intended to help security teams find and remediate exposure to compromised packages; it provides visibility into these controls rather than itself blocking packages. The article reports that the Miasma npm wave compromised 57 packages across more than 286 malicious versions and that Hades later compromised ensmallen and roughly two dozen related packages.

MITRE ATT&CK

Malware

Vendors

Products

Related Articles