Which versions of teeseest are malicious?

The following npm versions of teeseest are flagged malicious: 1.6.2. Treat any of these as compromised.

How do I remediate teeseest if I installed it?

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

If teeseest 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.

Is teeseest part of a known attack campaign?

Yes — teeseest is associated with the RLMA-2025-06513 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 teeseest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for teeseest (version 1.6.2).

Malicious package

teeseestnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

teeseest is a confirmed malicious npm package (MAL-2025-192878) that executes malicious code on install (malicious version 1.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in teeseest (npm)

MAL-2025-192878

Immediate action

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

npm uninstall teeseest

What this malware does

The package teeseest was found to contain malicious code.

Malicious versions

1 flagged

1.6.2

Indicators of compromise (SHA-256)

1b362dfc0cf88b484dc1471b3f18f368a403500a209857fd38ffd5ae53d13bd6

fb94e671955c53d31cf15ac9c62d74d57ae48e1da003cc63adbd0bcdd2f34776

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06513

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks teeseest-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