CRITICAL npm Malware

Malicious code in kanyut (npm)

MAL-2026-13819 · GHSA-7mmm-hmf4-g8vm

Published · Modified

Dependency scanning

Check whether kanyut is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (75dd1fedbe6fa65ad732715731698661fbe733cc186c28634d4f0424284dcbe7)

A a static rule matched on keyword co-occurrence (ping, GET, id) across widely separated lines in lib/Utils/generics.js. The matched tokens are consistent with ordinary HTTP client code and identifier handling within a utility module; no traced code path was identified that reads installer-side secrets (env vars, ~/.aws, ~/.ssh, ~/.npmrc, browser stores) or forwards them to an attacker-controlled destination, and no install-time lifecycle hook (preinstall/install/postinstall/prepare) or top-level side-effect execution was observed. The evidence available does not demonstrate an attacker benefit against a party installing the package.

Source: ghsa-malware (61ea3c365c950e3fe7c3e00e5f19b2722f15d20a20e2e991207337965588410b)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Ready to move

Start Securing

Free, no credit card | First findings in minutes