OpenSSF/OSV advisory MAL-2026-4299 confirms this npm version as malicious. 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...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @gbrlxvii/ts-project-lint (npm)
Details
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://git@192.168.0.1: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.
## Source: ghsa-malware (c73fbc270ffb4cf5f52bbfebfac578edea1d4b9eb3f84e9b2960e152832f6bce) 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.