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

trae-browser-inspectnpm

Malicious code in trae-browser-inspect (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1042
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall trae-browser-inspect

What this malware does

The package trae-browser-inspect was found to contain malicious code.

The OpenSSF Package Analysis project identified 'trae-browser-inspect' @ 9.9.9 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
9.9.9

Indicators of compromise (SHA-256)

fd5bf396be565b12f9c16a91a3d228cd650efde38a6ebf3b6656837d19adfdbb
2fbd2b8603f95aa744b92e1f624c31c4afc4dcb7ef634096a331302462b45e1f

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for trae-browser-inspect (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 trae-browser-inspect across your stack and pipelines.

  2. If you installed it — respond

    Remove trae-browser-inspect 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 activity or persistence.

  3. Did it already run?

    If trae-browser-inspect 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.

  4. How O3 protects you

    O3 blocks trae-browser-inspect 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. trae-browser-inspect 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.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks trae-browser-inspect-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

trae-browser-inspect (npm) malicious package — MAL-2026-1042 | O3 Security