Malicious code in @tekmidian/pai (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a26877c40609e311219c5193d5c1e2c50b5edf63913c0e4d7ad2be298e11f631) The package ships a bundled Node CLI under dist/ composed of multiple minified.mjs chunks (cli, cli2, hooks/worker-*, routing, project-setup, local-tiers, models-add, session-scan, hang-probe, config). Keyword co-occurrence rules match on tokens such as `PATH`, `ping`, `curl`, `GET`, `POST`, `Buffer.from(..., 'base64').toString(...)`, and example-domain strings (`curl https://example.com`, `curl http://localhost`, `curl http://x`) inside the bundles and in src/hooks/ts/lib/rules/builtin.generated.ts, which is a rules file enumerating example commands as inert data. The matches are spread across unrelated chunks and lines, consistent with a developer-agent/CLI codebase that references shell commands as sample inputs, rule patterns, and process-launching utilities rather than a hardcoded exfiltration path. No install or import lifecycle script is declared that would auto-run these paths, no attacker-controlled destination domain or IP is bound to a network sink, no read of installer-secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser or wallet stores) is tied to an outbound request, and the base64 decode sites are not wired to eval/exec of the decoded bytes. The observed signals are pattern co-occurrence in a minified bundle without a concrete installer-harm flow. ## Source: ghsa-malware (edec0655f6132f9a6bcf8c5025db3cbb86d2802ade88ab4f3acc6af4b3f40adb) 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 published

23 Oct 2026 00:56:39 UTC

Source modified

29 Oct 2026 14:30:32 UTC

Observed here

29 Oct 2026 15:12:22 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.