Which versions of winston-prisma are malicious?

The following npm versions of winston-prisma are flagged malicious: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.2.1, 1.2.2, 1.2.3. Treat any of these as compromised.

How do I remediate winston-prisma if I installed it?

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

If winston-prisma 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 winston-prisma part of a known attack campaign?

Yes — winston-prisma is associated with the RLMA-2026-02061 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 winston-prisma across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for winston-prisma (13 malicious versions).

Malicious package

winston-prismanpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

winston-prisma is a confirmed malicious npm package (MAL-2026-2805) that executes malicious code on install (malicious versions 1.1.0, 1.1.1, 1.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in winston-prisma (npm)

MAL-2026-2805

Immediate action

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

npm uninstall winston-prisma

What this malware does

The package winston-prisma was found to contain malicious code.

Malicious versions

13 flagged

1.1.01.1.11.1.21.1.31.1.41.1.51.1.61.1.71.1.81.1.91.2.11.2.21.2.3

Indicators of compromise (SHA-256)

a02b7c9577c812343d6a0e06c2ed73966ccdd260a3187e11de54c1c5bd8e5bbb

8bc2a581514f0a9f03ad807946bb8aa90ed013936e91ed2a413ced0966986921

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for winston-prisma (13 malicious versions).
If you installed it — respond
Remove winston-prisma 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 winston-prisma 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. winston-prisma on npm has been identified as a malicious package (versions 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02061

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks winston-prisma-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