Which versions of anidata-hds-maad are malicious?

Every published version of anidata-hds-maad on npm is considered malicious. Remove the package entirely.

How do I remediate anidata-hds-maad if I installed it?

anidata-hds-maad 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 anidata-hds-maad — how do I know if it already compromised me?

If anidata-hds-maad 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 anidata-hds-maad across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for anidata-hds-maad (all published versions).

Malicious package

anidata-hds-maadnpm

Advisory published Nov 12, 2025Updated Nov 12, 2025

anidata-hds-maad is a confirmed malicious npm package (MAL-2025-172957) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in anidata-hds-maad (npm)

MAL-2025-172957

Immediate action

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

npm uninstall anidata-hds-maad

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)

8134b5de742937c4de67788ea7d3eeff0581a4be64a079f14c997f9f75f62dcf

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for anidata-hds-maad (all published versions).
If you installed it — respond
anidata-hds-maad 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 anidata-hds-maad 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. anidata-hds-maad 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 anidata-hds-maad-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