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

@transaction-list/transaction-list-xsnpm

Malicious code in @transaction-list/transaction-list-xs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-476
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @transaction-list/transaction-list-xs

What this malware does

The package @transaction-list/transaction-list-xs was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b6a746b479fa4f5cf9daa56d99d4e405c183bae19f055d207078d1c166d76173

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 @transaction-list/transaction-list-xs (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @transaction-list/transaction-list-xs across your stack and pipelines.

  2. If you installed it — respond

    Remove @transaction-list/transaction-list-xs 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 @transaction-list/transaction-list-xs 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 @transaction-list/transaction-list-xs 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. @transaction-list/transaction-list-xs on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @transaction-list/transaction-list-xs-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.