Which versions of timelycare are malicious?

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

How do I remediate timelycare if I installed it?

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

If timelycare was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is timelycare part of a known attack campaign?

Yes — timelycare is associated with the RLMA-2026-05335, RLUA-2026-06521 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 timelycare across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for timelycare (version 1.0.0).

Malicious package

timelycarenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

timelycare is a confirmed malicious npm package (MAL-2026-7428) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in timelycare (npm)

MAL-2026-7428

Immediate action

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

npm uninstall timelycare

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c1b57ddc88e2f00acb7edb65b276fbb325183851aee5d42bc2d7ba5d08b382e5

7cbb93dfbc39636ecf2abdc23c10ec2412d5c9227a68445eb96da8a2aaad1a42

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for timelycare (version 1.0.0).
If you installed it — respond
Remove timelycare 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 timelycare was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. timelycare 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-05335RLUA-2026-06521

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks timelycare-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