Which versions of spytrack are malicious?

The following npm versions of spytrack are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate spytrack if I installed it?

spytrack is a typosquat — you almost certainly intended a legitimately-named package. Remove spytrack, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed spytrack — how do I know if it already compromised me?

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

Yes — spytrack is associated with the IN-MAL-2026-010625 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 spytrack across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spytrack (version 1.1.0).

Malicious package

spytracknpm

Advisory published Jul 15, 2026Updated Jul 15, 2026

spytrack is a confirmed malicious npm package (MAL-2026-10671) that typosquats a legitimate package to trick installs (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spytrack (npm)

MAL-2026-10671

Immediate action

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

npm uninstall spytrack

What this malware does

spytrack is a typosquat of chai-spies. When the plugin is registered via chai.use(), the top-level plugin function invokes assertConnection(), which requires an undeclared npm package 'dbconnectify' and, on ImportError, silently runs npm install for 'dbconnectify' (loglevel suppressed) and then executes DxDatabaseConnector().queryDBConnect(). The fetched package is not declared in package.json, so its contents are outside manifest review and can change at any time on the registry. The install-and-exec fires at plugin load in the installer's Node.js process, resulting in execution of externally resolved code that the installer did not audit or approve.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

72113145e88d53764f1e157c91cda05cb143a31802d9565ba8e1765e9886491b

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for spytrack (version 1.1.0).
If you installed it — respond
spytrack is a typosquat — you almost certainly intended a legitimately-named package. Remove spytrack, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If spytrack 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. spytrack on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010625

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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