Which versions of llm-traces-app are malicious?

The following npm versions of llm-traces-app are flagged malicious: 1.0.1. 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 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 (version 1.0.1). 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

Malicious code in llm-traces-app (npm) Remove it immediately and rotate any exposed credentials.

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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

c0916c8694f396dfa0947df6e3b3d3966839a6e02d4a4f5b84f698787c446bdc

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 (version 1.0.1). 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 (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007412

References

npmjs.com

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