Which versions of gitpath-package are malicious?

The following npm versions of gitpath-package are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate gitpath-package if I installed it?

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

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

Yes — gitpath-package is associated with the RLMA-2026-05102, RLUA-2026-06261 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 gitpath-package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gitpath-package (3 malicious versions).

Malicious package

gitpath-packagenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in gitpath-package (npm)

MAL-2026-7292

Immediate action

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

npm uninstall gitpath-package

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

f3bf74b018c64dd4bb5c689926d73e4f2a2135866eb07f95f712628adeaec00b

fbd5ba3fa2de335512bea7e3752e6a1863b5f913be2a5f0861d418070513cb0e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05102RLUA-2026-06261

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks gitpath-package-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