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

srcsrctestnpm

Malicious code in srcsrctest (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2235
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall srcsrctest

What this malware does

The package srcsrctest was found to contain malicious code.

The OpenSSF Package Analysis project identified 'srcsrctest' @ 1.0.6 (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

2 flagged
1.0.31.0.6

Indicators of compromise (SHA-256)

1aa147cd1bafdb2bf26b1c157edac9d3765ce544456e7f4e0fde95cd269af777
9049c460c15f43120e5e8bb1207b5a642536124c66ff3dc7863e679e9d46b26e
a44b46855732b5a5522c0a1ea3ef88d5977daad1bfa5c39b42e0324e52fcf6f8

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

  2. If you installed it — respond

    Remove srcsrctest 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 srcsrctest 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 srcsrctest 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. srcsrctest on npm has been identified as a malicious package (versions 1.0.3, 1.0.6 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 srcsrctest-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.

srcsrctest (npm) malicious package — MAL-2026-2235 | O3 Security