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

@3stripes/api-clientnpm

Malicious code in @3stripes/api-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1424
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @3stripes/api-client

What this malware does

The package @3stripes/api-client was found to contain malicious code.

The OpenSSF Package Analysis project identified '@3stripes/api-client' @ 999.0.2 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
999.0.2

Indicators of compromise (SHA-256)

a25a3f6f0b4ff00af8eca4dcea0bfdb698f071423a6b30b1b62a440b71137688
1644f08d12a97a4daeeca3e4195d91585bdbe1a8c2085fa918a92427cf1ee99f

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 @3stripes/api-client (version 999.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @3stripes/api-client across your stack and pipelines.

  2. If you installed it — respond

    Remove @3stripes/api-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 @3stripes/api-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 @3stripes/api-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. @3stripes/api-client on npm has been identified as a malicious package (version 999.0.2 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 @3stripes/api-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.

Malware detection Runtime egress monitoring