Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

amazon-q-developer-streaming-clientnpm

Malicious code in amazon-q-developer-streaming-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3016
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall amazon-q-developer-streaming-client

What this malware does

The package amazon-q-developer-streaming-client was found to contain malicious code.

The OpenSSF Package Analysis project identified 'amazon-q-developer-streaming-client' @ 99.9.13 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
99.9.1199.9.1399.9.15

Indicators of compromise (SHA-256)

bedb03611546444363288fafa5c9320d572a8fc1bcbfd52a1886076523c182d7
ca380d122effc585a4688a2463b822cba039581576471979a57f4bf67cf505b3
2612d348229614bb857a8f2c30c1ad2d66954d7a05073f15319f8aca2fb1a86d
2b62909108b789f041fc590407cb04c9e9d85d5ba7071c9573c98f981a8caed2

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for amazon-q-developer-streaming-client (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amazon-q-developer-streaming-client across your stack and pipelines.

  2. If you installed it — respond

    Remove amazon-q-developer-streaming-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If amazon-q-developer-streaming-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks amazon-q-developer-streaming-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. amazon-q-developer-streaming-client on npm has been identified as a malicious package (versions 99.9.11, 99.9.13, 99.9.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks amazon-q-developer-streaming-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

amazon-q-developer-streaming-client (npm) malicious package — MAL-2026-3016 | O3 Security