Which versions of tscom-geo are malicious?

The following npm versions of tscom-geo are flagged malicious: 99.99.9. Treat any of these as compromised.

How do I remediate tscom-geo if I installed it?

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

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

Yes — tscom-geo is associated with the RLMA-2026-01625 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 tscom-geo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tscom-geo (version 99.99.9).

Malicious package

tscom-geonpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

tscom-geo is a confirmed malicious npm package (MAL-2026-1868) that executes malicious code on install (malicious version 99.99.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tscom-geo (npm)

MAL-2026-1868

Immediate action

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

npm uninstall tscom-geo

What this malware does

The package tscom-geo was found to contain malicious code.

Malicious versions

1 flagged

99.99.9

Indicators of compromise (SHA-256)

847c43632bdc73c5c1a53011fbc60ce0126cd1fea61692fa681599d3c4eaac27

1ac03439d7de860a9ae4215787b0a541834ac38155dd596d163607099107197f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01625

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tscom-geo-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