What does the srcsrctest malware do?

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.

Which versions of srcsrctest are malicious?

The following npm versions of srcsrctest are flagged malicious: 1.0.3, 1.0.6. Treat any of these as compromised.

How do I remediate srcsrctest if I installed it?

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.

I already installed srcsrctest — how do I know if it already compromised me?

If srcsrctest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find srcsrctest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for srcsrctest (2 malicious versions).

Malicious package

srcsrctestnpm

Advisory published Mar 26, 2026Updated Mar 31, 2026

srcsrctest is a confirmed malicious npm package (MAL-2026-2235) that executes malicious code on install (malicious versions 1.0.3, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in srcsrctest (npm)

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

Find it
Search your lockfiles and build artifacts for srcsrctest (2 malicious versions).
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.
Did it already run?
If srcsrctest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database