Which versions of trgrip are malicious?

Every published version of trgrip on npm is considered malicious. Remove the package entirely.

How do I remediate trgrip if I installed it?

trgrip establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

How do I find trgrip across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for trgrip (all published versions).

Malicious package

trgripnpm

Advisory published Apr 15, 2026Updated Apr 23, 2026

trgrip is a confirmed malicious npm package (MAL-2026-2912) that opens a backdoor for remote access. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in trgrip (npm)

MAL-2026-2912

Immediate action

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

npm uninstall trgrip

What this malware does

trgrip is a malicious npm package that when imported downloads a C2 dropper from https://44.206.172[.]239:7443/direct/download/97900a0e-c691-483a-a988-97b76f205c0f and executes it.

The package trgrip was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

3b787c102a6313ef9eaafaedccd83ab634da290283df07b97c4c4eb62117ad55

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for trgrip (all published versions).
If you installed it — respond
trgrip establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If trgrip 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. trgrip on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

indece.com

Credits

Amazon Inspector · finder
indece · finder

Detect & block this

O3 blocks trgrip-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database