Which versions of tescoutils are malicious?

The following npm versions of tescoutils are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate tescoutils if I installed it?

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

If tescoutils 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 tescoutils part of a known attack campaign?

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

Search your lockfiles and build artifacts for tescoutils (2 malicious versions).

Malicious package

tescoutilsnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

tescoutils is a confirmed malicious npm package (MAL-2025-192879) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tescoutils (npm)

MAL-2025-192879

Immediate action

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

npm uninstall tescoutils

What this malware does

The package tescoutils was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

0dc8434c3f69a27464d6ae4f7d6ce4d6cf2600cfd63d153405dde3d892bafccb

64babfcdec855007803f08c8c8b149b06c85ff017430ddeec4a2c9aa90c0897e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06516

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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