Which versions of @miptaa02/team are malicious?

Every published version of @miptaa02/team on npm is considered malicious. Remove the package entirely.

How do I remediate @miptaa02/team if I installed it?

@miptaa02/team 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 @miptaa02/team — how do I know if it already compromised me?

If @miptaa02/team 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 @miptaa02/team across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @miptaa02/team (all published versions).

Part of a larger attack: @miptaa02 published 579 malicious packages. See the full campaign →

Malicious package

@miptaa02/teamnpm

Advisory published Nov 12, 2025Updated Nov 12, 2025

@miptaa02/team is a confirmed malicious npm package (MAL-2025-150970) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @miptaa02/team (npm)

MAL-2025-150970

Immediate action

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

npm uninstall @miptaa02/team

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)

30ab53404de97e12ba877e1698bf00c4bb3fbe8e9c7e87c4f75bf2dd8e08d7f7

Detection & response playbook

Credential / info stealer

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