Which versions of claude-code-timer are malicious?

The following npm versions of claude-code-timer are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate claude-code-timer if I installed it?

claude-code-timer 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 claude-code-timer — how do I know if it already compromised me?

If claude-code-timer 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 claude-code-timer part of a known attack campaign?

Yes — claude-code-timer is associated with the RLMA-2026-05515, IN-MAL-2026-013183, RLUA-2026-06153 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 claude-code-timer 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 claude-code-timer (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 claude-code-timer across your stack and pipelines.

Malicious package

claude-code-timernpm

claude-code-timer is a confirmed malicious npm package (MAL-2026-10892) 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 claude-code-timer (npm)

MAL-2026-10892

Immediate action

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

npm uninstall claude-code-timer

What this malware does

[email protected] was scanned with no findings of concern. No install-time lifecycle scripts, no outbound network calls to attacker-controlled destinations, no credential or environment scraping, no dropper or fetch-and-execute pattern, and no silent-relay behavior were observed. The package does not exhibit any of the supply-chain attack fingerprints this system is designed to catch.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

47c8fbd95aebea78e97482eb6c675285a6640d59e9e8de9cde2203e520c4e234

04950731ec6589eebae22166fb042e4253719f71bfd3fc2b58f28d26ede9e43c

b3d896e45fc4fb4506eae232dd8a7bbbaa4431b2ce5e42109f16dedfa7085e9b

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 claude-code-timer (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 claude-code-timer across your stack and pipelines.
If you installed it — respond
claude-code-timer 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 claude-code-timer 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 claude-code-timer 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. claude-code-timer 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

RLMA-2026-05515IN-MAL-2026-013183RLUA-2026-06153

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks claude-code-timer-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