Which versions of @quickcall/krew are malicious?

The following npm versions of @quickcall/krew are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate @quickcall/krew if I installed it?

Remove @quickcall/krew 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.

I already installed @quickcall/krew — how do I know if it already compromised me?

If @quickcall/krew 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 @quickcall/krew part of a known attack campaign?

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

Malicious package

@quickcall/krewnpm

@quickcall/krew is a confirmed malicious npm package (MAL-2026-10494) that executes malicious code on install (malicious version 0.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @quickcall/krew (npm)

MAL-2026-10494

Immediate action

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

npm uninstall @quickcall/krew

What this malware does

The quickcall CLI unconditionally starts a telemetry sync daemon at startup (dist/main.js invokes startSyncDaemon() and registers a session-end hook plus a 10-second flush interval). On every session, the daemon POSTs the entire coding-agent transcript — user prompts, model outputs, tool calls, tool results (which include file contents the agent reads and stdout/stderr of bash commands run on the developer's machine) — together with os.hostname(), current working directory, and git branch/commit/remote URL to https://trace.quickcall.dev/api/krew/sessions. The destination URL and an embedded API key (qt_push_krew_87edcbb6-1f1e-4960-ab56-1f81d1638526) are hardcoded as defaults in dist/core/telemetry-config.js (lines 14-16); the optional env-var overrides (QUICKCALL_TELEMETRY_URL, QUICKCALL_TELEMETRY_KEY) keep the relay enabled by default for any user who does not set them. There is no README disclosure of this behavior and no obvious opt-out flag. Because a coding-agent session routinely contains source code under development, secrets pasted into prompts, and the output of arbitrary shell commands executed on the developer's host, every normal use of the advertised CLI silently leaks caller-supplied data to the publisher's endpoint. Trigger is CLI startup (not npm install, not require()), but it is the documented and only invocation path for this tool.

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

cef7755bfdd2bf753ace888115fd963d8c44147bcf715a0e276f4c6d36208770

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @quickcall/krew (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @quickcall/krew across your stack and pipelines.
If you installed it — respond
Remove @quickcall/krew 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 @quickcall/krew 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 @quickcall/krew 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. @quickcall/krew on npm has been identified as a malicious package (version 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010322

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @quickcall/krew-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database