Which versions of llm-traces-app are malicious?

The following npm versions of llm-traces-app are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate llm-traces-app if I installed it?

llm-traces-app is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed llm-traces-app — how do I know if it already compromised me?

If llm-traces-app 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 llm-traces-app part of a known attack campaign?

Yes — llm-traces-app is associated with the IN-MAL-2026-007412, GHSA-xcwg-9ggx-j7pm, IN-MAL-2026-019828 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 llm-traces-app 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 llm-traces-app (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llm-traces-app across your stack and pipelines.

Malicious package

llm-traces-appnpm

llm-traces-app is a confirmed malicious npm package (MAL-2026-6371) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in llm-traces-app (npm)

MAL-2026-6371

Immediate action

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

npm uninstall llm-traces-app

What this malware does

On npm install, the package's preinstall lifecycle hook runs node index.js, which collects host identity (os.hostname(), os.userInfo(), homedir, DNS servers, cwd) and reads the installer's /etc/passwd and /etc/hosts, then HTTPS POSTs the combined payload to ltiyq4zyhrs88zgp5lef9hbec5i46uuj.oastify.com — a Burp Collaborator (OAST) subdomain controlled by the package publisher. The exfiltration fires automatically on default install with no user interaction. Reading /etc/passwd enumerates the installer's local user accounts; the OAST destination provides the publisher with arbitrary out-of-band data capture. This is a textbook dependency-confusion / supply-chain exfiltration beacon.

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

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

c0916c8694f396dfa0947df6e3b3d3966839a6e02d4a4f5b84f698787c446bdc

745b957a8874cad0ca26286f04294354427e1ea01ba4f815d78d1b7f3ebdd2a8

cd801ba64f062e1c35bea3dc38a310ed65f563a68386c16c6f4d734adf1ab7c2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for llm-traces-app (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llm-traces-app across your stack and pipelines.
If you installed it — respond
llm-traces-app is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If llm-traces-app 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 llm-traces-app 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. llm-traces-app on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007412GHSA-xcwg-9ggx-j7pmIN-MAL-2026-019828

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks llm-traces-app-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database