Which versions of awk-node-public-interpret-cron are malicious?

Every published version of awk-node-public-interpret-cron on npm is considered malicious. Remove the package entirely.

How do I remediate awk-node-public-interpret-cron if I installed it?

Remove awk-node-public-interpret-cron 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 awk-node-public-interpret-cron — how do I know if it already compromised me?

If awk-node-public-interpret-cron 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 awk-node-public-interpret-cron across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for awk-node-public-interpret-cron (all published versions).

Malicious package

awk-node-public-interpret-cronnpm

Advisory published Nov 13, 2025Updated Nov 13, 2025

awk-node-public-interpret-cron is a confirmed malicious npm package (MAL-2025-185708) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in awk-node-public-interpret-cron (npm)

MAL-2025-185708

Immediate action

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

npm uninstall awk-node-public-interpret-cron

What this malware does

This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The malicious payload modifies package.json to remove private flags, changes version numbers, generates random Indonesian-themed package names (some variants are also in English), and continuously republishes variants to pollute the npm registry.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

7e72184d33130eb0661746bef8ae65da6a9d81b8319bca387ad8374ec909da7c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for awk-node-public-interpret-cron (all published versions).
If you installed it — respond
Remove awk-node-public-interpret-cron 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 awk-node-public-interpret-cron 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. awk-node-public-interpret-cron 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.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks awk-node-public-interpret-cron-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