Which versions of internallib_v657 are malicious?

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

How do I remediate internallib_v657 if I installed it?

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

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

Yes — internallib_v657 is associated with the IN-MAL-2026-020497 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_v657 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_v657 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v657 across your stack and pipelines.

Malicious package

internallib_v657npm

internallib_v657 is a confirmed malicious npm package (MAL-2026-16482) 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_v657 (npm)

MAL-2026-16482

Immediate action

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

npm uninstall internallib_v657

What this malware does

index.js exports a command() function that invokes /bin/bash -c to curl a reverse-shell payload from reverse-shell.sh targeted at the hardcoded IP 10.0.73.186:443 and pipes it to sh. Any consumer that requires this package and calls the exported function receives a full interactive remote shell to that address, giving the remote party arbitrary command execution on the installer's host. The package has generic naming, empty metadata, and a cover string, and provides no legitimate functionality alongside the backdoor.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

d61ffc921e9432c8176cc16265daf6add48cf90a4f99ec6bbec173e5109673b1

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_v657 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v657 across your stack and pipelines.
If you installed it — respond
internallib_v657 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_v657 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_v657 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_v657 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

IN-MAL-2026-020497

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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