Which versions of log-taker are malicious?

The following npm versions of log-taker are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate log-taker if I installed it?

log-taker 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 log-taker — how do I know if it already compromised me?

If log-taker 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 log-taker part of a known attack campaign?

Yes — log-taker is associated with the IN-MAL-2026-007361 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 log-taker 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 log-taker (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging log-taker across your stack and pipelines.

Malicious package

log-takernpm

Malicious code in log-taker (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6338

Immediate action

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

npm uninstall log-taker

What this malware does

index.js requires child_process and invokes execSync with bash and zsh shells (around lines 315 and 331). The available evidence does not establish what commands are run, whether the calls fire at install/import time or only when a caller invokes a specific exported function, or whether any installer data is exfiltrated to a network destination. The package name suggests a log-collection tool, which can legitimately shell out to system utilities, but the shell-execution surface combined with the absence of clear scoping warrants human review of the actual command strings and reachability before recommending the package to installers.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

35623f56ea43d8a9a7ac1caa84678ed40d6923fdf19d8d23f7d4aacdde1a8c4a

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 log-taker (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging log-taker across your stack and pipelines.
If you installed it — respond
log-taker 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 log-taker 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 log-taker 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. log-taker on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007361

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks log-taker-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