Which versions of teate-thy-sonic-burne are malicious?

The following npm versions of teate-thy-sonic-burne are flagged malicious: 6.9.9. Treat any of these as compromised.

How do I remediate teate-thy-sonic-burne if I installed it?

teate-thy-sonic-burne 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 teate-thy-sonic-burne — how do I know if it already compromised me?

If teate-thy-sonic-burne was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is teate-thy-sonic-burne part of a known attack campaign?

Yes — teate-thy-sonic-burne is associated with the RLMA-2026-06519 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 teate-thy-sonic-burne across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for teate-thy-sonic-burne (version 6.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging teate-thy-sonic-burne across your stack and pipelines.

Malicious package

teate-thy-sonic-burnenpm

teate-thy-sonic-burne is a confirmed malicious npm package (MAL-2025-180225) that steals credentials and exfiltrates sensitive data (malicious version 6.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in teate-thy-sonic-burne (npm)

MAL-2025-180225

Immediate action

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

npm uninstall teate-thy-sonic-burne

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

1 flagged

6.9.9

Indicators of compromise (SHA-256)

515314647c968a1389da6a54dd90d298ad729ff903c84e0b8785fd714d4d56d8

bcf8aed888ba7ce0ded345a1a8e6447b7e5be830d24291b896fb2b0e19b04ed5

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for teate-thy-sonic-burne (version 6.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging teate-thy-sonic-burne across your stack and pipelines.
If you installed it — respond
teate-thy-sonic-burne 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 teate-thy-sonic-burne was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks teate-thy-sonic-burne before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. teate-thy-sonic-burne on npm has been identified as a malicious package (version 6.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-06519

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks teate-thy-sonic-burne-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