Which versions of tombac-chronos are malicious?

Every published version of tombac-chronos on npm is considered malicious. Remove the package entirely.

How do I remediate tombac-chronos if I installed it?

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

If tombac-chronos 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.

How do I find tombac-chronos across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tombac-chronos (all published versions).

Malicious package

tombac-chronosnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in tombac-chronos (npm)

MAL-2026-2418

Immediate action

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

npm uninstall tombac-chronos

What this malware does

Suspicious install script executing index.js and an untrustworthy author email domain sl4x0.xyz strongly suggest this package is malware.

The package tombac-chronos was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

69e040ef4bdedbed143a5a8d1a1bb0389fa07848772a87c03da1c67557ced13e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tombac-chronos (all published versions).
If you installed it — respond
Remove tombac-chronos 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 tombac-chronos 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. tombac-chronos on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks tombac-chronos-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