Which versions of path-internal-util are malicious?

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

How do I remediate path-internal-util if I installed it?

path-internal-util is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed path-internal-util — how do I know if it already compromised me?

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

Yes — path-internal-util is associated with the IN-MAL-2026-005250, IN-MAL-2026-005249, GHSA-c267-q765-387r, RLMA-2026-05207, RLUA-2026-05593 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 path-internal-util 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 path-internal-util (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging path-internal-util across your stack and pipelines.

Malicious package

path-internal-utilnpm

Malicious code in path-internal-util (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3312

Immediate action

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

npm uninstall path-internal-util

What this malware does

On require(), path.js executes an IIFE that calls loadTokenData(), which fetches a base64-obfuscated URL (decoding to https://www.jsonkeeper.com/b/CWOV9), parses the JSON response, and passes data.content directly to eval(). The remote paste is mutable by whoever controls the jsonkeeper entry, so any installer that imports the package executes arbitrary attacker-controlled JavaScript in-process at import time. The package name impersonates Node's built-in path module and the README claims to be 'an exact copy of the NodeJS path module', increasing the chance of accidental installation by developers seeking a path polyfill.

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.

The OpenSSF Package Analysis project identified 'path-internal-util' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

db91c8a40ff204e2aa98c594413d69b624d93a4ac51ea09fc00b1d3f63b8e462

3bd4ebaf2978cb19cb80932842460fcb683c7e5867ec9e51c642bc29605394d4

a5333e8bbb96471236eb31d7ee684d66437fdbf8a055cd9e15cd76f417adab51

aaba59a63a7a6f3dfc734a55082dff17dbf357f41b2a09ef0c87f73d046088e1

256c0d663976ed956c5fde6343acb9a6e640443a0091911fd4a2a57ab49e14f3

0b8c2e1d81ba7400018f86d8db6926abdf36b9eaf02c186ae07f5d6ae477a845

551116bd02887493c0429c83a46d433d6ddf4b1c32553993ed0098b2ceb38c95

6c67b4e7637f28440f04349c9cec81cdd594a927362d1919adc1dae394c1eb3d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for path-internal-util (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging path-internal-util across your stack and pipelines.
If you installed it — respond
path-internal-util is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If path-internal-util 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 path-internal-util 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. path-internal-util 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

IN-MAL-2026-005250IN-MAL-2026-005249GHSA-c267-q765-387rRLMA-2026-05207RLUA-2026-05593

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks path-internal-util-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring