Which versions of kanyut are malicious?

The following npm versions of kanyut are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate kanyut if I installed it?

kanyut is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed kanyut — how do I know if it already compromised me?

If kanyut was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is kanyut part of a known attack campaign?

Yes — kanyut is associated with the GHSA-7mmm-hmf4-g8vm, IN-MAL-2026-017513 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find kanyut across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kanyut (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kanyut across your stack and pipelines.

Malicious package

kanyutnpm

kanyut is a confirmed malicious npm package (MAL-2026-13819) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kanyut (npm)

MAL-2026-13819

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall kanyut

What this malware does

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.

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

61ea3c365c950e3fe7c3e00e5f19b2722f15d20a20e2e991207337965588410b

75dd1fedbe6fa65ad732715731698661fbe733cc186c28634d4f0424284dcbe7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kanyut (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kanyut across your stack and pipelines.
If you installed it — respond
kanyut is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If kanyut was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks kanyut before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. kanyut on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7mmm-hmf4-g8vmIN-MAL-2026-017513

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kanyut-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database