Threats Tagged 'mal-2026-5218'

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e1bce8c001a8e85b493ccdd8af1e3e57f3578d1026e6d5d147374b0a68467313) autotel-devtools ships bundled CommonJS and ESM artifacts (dist/cli.cjs, dist/cli.js, dist/index.cjs, dist/index.js, dist/server/index.cjs, dist/server/index.js, dist/widget.global.js) where pattern matches surfaced co-occurrence of Buffer.from(..., 'base64') decoding alongside HTTP POST and 'ping' tokens. The package is presented as a developer-tools CLI/server, which legitimately bundles command names and HTTP clients into a single rollup output, and the matched primitives are consistent with that shape (e.g. base64 token decoding, POST against a configurable backend, a 'ping' subcommand or health-check string). No specific attacker-controlled destination, env-var scraping, credential path read, or install-time lifecycle hook was identified, and the keyword proximity inside minified bundles is the weakest evidence shape. A human reviewer should de-minify the relevant spans around dist/cli.cjs:534 and dist/index.cjs:143 to confirm whether the POST destinations are user-configurable backends or a hardcoded endpoint, and whether the base64 decode handles a JWT/session token or executes decoded bytes. ## Source: ghsa-malware (1d9ead83772087e781dd41428b81aec15c104b5064f20f0c47e911025942bd01) 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. ## Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb) The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized `binding.gyp` files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.