Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

internallib_v275npm

Advisory published Updated

internallib_v275 is a confirmed malicious npm package (MAL-2026-17510) 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_v275 (npm)

MAL-2026-17510
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall internallib_v275

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 targeting the hardcoded host 10.0.49.106:443 and pipes the response to sh, yielding interactive remote shell access on the installer host whenever the exported API is called. The fetch-and-execute path has no pinning, no hash verification, and runs over an unauthenticated network retrieval. package.json also declares a self-referential dependency on internallib_v275@^1.0.0, a dependency-confusion shape consistent with a package targeting an internal registry namespace so that resolution against the public registry pulls this backdoor into internal builds.

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)

80c1c6d383b3defb01da235e39e08ce56276d887e63d900aea2ee689836f71b4
7e73d7869fce3c750cb3bdd88167659dd362d142c79a91f25408221ebacdf3e6

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for internallib_v275 (version 1.0.3).

  2. If you installed it — respond

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

  3. Did it already run?

    If internallib_v275 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. internallib_v275 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

IN-MAL-2026-020969GHSA-f6rc-jhj3-4p2w

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks internallib_v275-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

internallib_v275 (npm) malicious package — MAL-2026-17510 | O3 Security