Which versions of adobe_pipeline_test are malicious?

The following npm versions of adobe_pipeline_test are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate adobe_pipeline_test if I installed it?

Remove adobe_pipeline_test 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 adobe_pipeline_test — how do I know if it already compromised me?

If adobe_pipeline_test 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.

Is adobe_pipeline_test part of a known attack campaign?

Yes — adobe_pipeline_test is associated with the RLMA-2026-01095 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

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

Search your lockfiles and build artifacts for adobe_pipeline_test (version 1.0.0).

Malicious package

adobe_pipeline_testnpm

Advisory published Feb 6, 2026Updated Mar 19, 2026

adobe_pipeline_test is a confirmed malicious npm package (MAL-2026-783) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adobe_pipeline_test (npm)

MAL-2026-783

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall adobe_pipeline_test

What this malware does

The package adobe_pipeline_test was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f7e438937c9c04fd06645a505f5bd509ee3c1fa942be02cefa881023f849b781

d37e4eb0b93e704503c8725558f2a471e9a98ddf7762951ae86540ce518a8963

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for adobe_pipeline_test (version 1.0.0).
If you installed it — respond
Remove adobe_pipeline_test 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 adobe_pipeline_test 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. adobe_pipeline_test on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01095

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks adobe_pipeline_test-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