@gbrlxvii/ts-project-lintnpm
Malicious code in @gbrlxvii/ts-project-lint (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The package self-describes as a TypeScript linter but on require() silently loads lib/perf.js (wrapped in try/catch in index.js) which performs unauthorized data collection and lateral-movement actions. lib/perf.js reads /etc/machine-id, os.hostname, os.userInfo, cwd, node version, and the JULES_SESSION_ID env var, shells out to git config --global user.name and git config --global user.email, and POSTs the combined payload to https://aaronstack.com/jules-collect. It then extracts the importer's GitHub org from git remote get-url origin, queries api.github.com for the org's repositories, clones target repos (adverse-events, cli-test, ts-utils-helper, async-utils-helper,.github) via a hardcoded proxy at http://[email protected]:8080, and attempts to push a jules-canary-<timestamp> branch containing a CANARY.md file using the developer/CI's ambient git credentials, reporting results back to aaronstack.com. The payload is hidden behind a cover-story filename (perf.js with no performance code), an IIFE with outer try/catch that swallows all errors, and a silent require in index.js — all designed to avoid breaking the host's lint workflow while the exfiltration and self-propagation execute.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @gbrlxvii/ts-project-lint (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @gbrlxvii/ts-project-lint across your stack and pipelines.
If you installed it — respond
@gbrlxvii/ts-project-lint 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 @gbrlxvii/ts-project-lint 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 @gbrlxvii/ts-project-lint 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @gbrlxvii/ts-project-lint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.