If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (70d52b44b46819aa61ff57d4863315b09f655a4fb5b5787843c2a24f85d9c6db)
The package's package.json declares a preinstall hook `bun run index.js` and lists the Bun runtime (`bun ^1.3.13`) as a dependency, causing an obfuscated ~500KB index.js to execute automatically on `npm install` under a non-Node runtime. index.js is packed with obfuscator.io (rotated string array `_0x71ec`) and additionally implements a custom PBKDF2/HMAC-derived cipher whose decrypt function is installed on globalThis; the fetch base URL and User-Agent are reconstructed at runtime from encoded string-array indices rather than appearing as plaintext literals. The payload calls the GitHub API with an Authorization Bearer token, inspects the `X-OAuth-Scopes` response header for `repo` and `workflow` scopes, and enumerates `/user/orgs` — token triage and org enumeration unrelated to the package's stated i18n/translation purpose. index.js is not listed in package.json's declared `files` array (`bin`, `dist`, `types`, `README.md`) yet ships at the tarball root and is referenced by the preinstall script, indicating the payload sits outside the author's declared publish surface.
Source: ghsa-malware (6567fe3822e10873e7be53d7b830f525aa2fc5efc3083c0fe2b713bd896220eb)
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.