Which versions of @ts-internal/shared-lib are malicious?

The following npm versions of @ts-internal/shared-lib are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate @ts-internal/shared-lib if I installed it?

@ts-internal/shared-lib 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 @ts-internal/shared-lib — how do I know if it already compromised me?

If @ts-internal/shared-lib 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 @ts-internal/shared-lib part of a known attack campaign?

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

Malicious package

@ts-internal/shared-libnpm

Malicious code in @ts-internal/shared-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5863

Immediate action

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

npm uninstall @ts-internal/shared-lib

What this malware does

The package squats the internal-looking scope @ts-internal/shared-lib on the public npm registry and runs a network beacon both during install (preinstall and postinstall hooks invoke node lifecycle.js) and on module load (index.js calls require('./beacon').beacon('require')). beacon.js collects os.hostname(), os.userInfo().username, process.cwd(), os.platform(), and the package name/version, hex-encodes the blob, and transmits it via DNS lookup and HTTPS GET to d8oa6q03t3o2ksbjirogwxiwiyhp6e57o.oast.site (an interactsh OAST collector) and npm-dc-seek-1781572474.testingboxes.com. Any build that misresolves this name to the public registry will silently leak identifying host metadata to two third-party endpoints. The README self-describes the package as a dependency-confusion proof-of-concept, but installers cannot consent and cannot verify researcher authorization; the squat-plus-beacon mechanism is the attack regardless of stated intent.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

7afc836ea4b9ecc7e09f0add976470f1b4e253f8b5b53b3ce706889efb349171

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

Campaign

IN-MAL-2026-006747

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ts-internal/shared-lib-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