katal-loggernpm
katal-logger is a confirmed malicious npm package (MAL-2026-15513) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in katal-logger (npm)
What this malware does
package.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/katal-logger) instead of a registry version range. On npm install, npm fetches whatever bytes that URL currently returns and installs them as the package, executing any lifecycle scripts contained inside. There is no version pin, no integrity/hash check, and the host is unrelated to the npm registry, so control over repo.securityctrl.com equates to code execution on the installing machine. The dependency key equals the package's own name (dependency-confusion shape) and the shipped index.js is an inert stub, so the manifest line is the entire delivery mechanism — the absence of scripts in this tarball does not mitigate the fetch.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for katal-logger (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging katal-logger across your stack and pipelines.
If you installed it — respond
Remove katal-logger from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If katal-logger 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 katal-logger 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks katal-logger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.