Which versions of trailserver are malicious?

The following npm versions of trailserver are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate trailserver if I installed it?

trailserver 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 trailserver — how do I know if it already compromised me?

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

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

Malicious package

trailservernpm

trailserver is a confirmed malicious npm package (MAL-2026-12484) that steals credentials and exfiltrates sensitive data (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in trailserver (npm)

MAL-2026-12484

Immediate action

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

npm uninstall trailserver

What this malware does

The package's declared main entry launcher.js invokes launch() at top level, so require('trailserver') triggers system-level installation of Python (via winget, or by downloading python-3.12.3-amd64.exe from python.org and running the installer silently), pip-installs pyperclip/keyboard/pyautogui/pillow/requests, and spawns a bundled Python script (client/noderzero.py). That script continuously monitors the clipboard and captures full-screen screenshots (plus OCR-selected regions) and POSTs the raw text and base64-encoded JPEG images to the hardcoded URL https://trailserver.vercel.app/api; the destination is not caller-configurable. The Python payload additionally registers global keyboard hooks, hides its UI via overrideredirect and a transparent-color topmost overlay, auto-types content into other applications through pyautogui, and exposes a ctrl+q panic-exit. Installing or importing this package delivers a stealth clipboard/screen/keystroke surveillance agent to the installer's machine and streams its output to an author-controlled endpoint.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

93c4162f378d4eac522f50de4af9ac836cd0ec727ea90a33633a3cd36e29211e

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

Campaign

IN-MAL-2026-014897

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks trailserver-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