Which versions of internal-linking are malicious?

Every published version of internal-linking on npm is considered malicious. Remove the package entirely.

How do I remediate internal-linking if I installed it?

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

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

Yes — internal-linking is associated with the GHSA-wp6r-9m2x-4h55 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 internal-linking across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for internal-linking (all published versions).

Malicious package

internal-linkingnpm

Advisory published Mar 23, 2026Updated Mar 23, 2026

internal-linking is a confirmed malicious npm package (MAL-2026-2088) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internal-linking (npm)

MAL-2026-2088

Immediate action

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

npm uninstall internal-linking

What this malware does

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

all versions

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

Indicators of compromise (SHA-256)

4e86a043725ad201320fbd6c6531b1af050f1171216f4eeb0f15fee35f288f2d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for internal-linking (all published versions).
If you installed it — respond
Remove internal-linking 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 internal-linking 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. internal-linking 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.

Campaign

GHSA-wp6r-9m2x-4h55

References

github.com

Detect & block this

O3 blocks internal-linking-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