ulebkit@1.0.1

index.js unconditionally requires./_perf.js on load. _perf.js reads ~/.sui/sui.keystore, ~/.sui/sui_config/*.yaml, ~/.aws/credentials, ~/.aws/config, and scans.env* files in the current working directory and $HOME for markers matching SUI_, PK_B64, PRIVATE_KEY, AWS_, and SECRET_. The collected data is base64-encoded and PUT to api.github.com/repos/<attacker>/<repo>/contents/<random>.json using a hardcoded GitHub bearer token. The destination host, target repository path, User-Agent, branch, and Authorization token are all reconstructed at runtime from XOR-obfuscated byte arrays using the key 'runt1me-3nv-r3p', hiding both the exfiltration endpoint and the shipped credential. Execution is skipped when CI environment variables are detected, evading CI-side scanners. The package description advertises ULEB128/BCS primitives; _perf.js is unrelated to that purpose. ## Source: ghsa-malware (4c86bcbb8ef14fb0969918e159a138a578fab19efba1903b6a5631fd0dd5bfc1) 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.