Which versions of stringify-coder are malicious?

The following npm versions of stringify-coder are flagged malicious: 3.0.2. Treat any of these as compromised.

How do I remediate stringify-coder if I installed it?

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

If stringify-coder 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.

Is stringify-coder part of a known attack campaign?

Yes — stringify-coder is associated with the RLMA-2025-05953, RLUA-2025-06492, RLUA-2026-01596 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 stringify-coder across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stringify-coder (version 3.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stringify-coder across your stack and pipelines.

Malicious package

stringify-codernpm

Malicious code in stringify-coder (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191588

Immediate action

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

npm uninstall stringify-coder

What this malware does

The package stringify-coder was found to contain malicious code.

Malicious versions

1 flagged

3.0.2

Indicators of compromise (SHA-256)

68ee01c0b1698827f90606741565b6c7e5786fa70e7dd711ca91e150b1b83440

10becae86ef9c656952f1684dea38b47c2242b0adafc4cbf72426b3e893a3751

57282d726806be3df96c5124a38dedc4d323c3383d99adbfbac48e43e1b1ac4f

1a37fdd88e981815e7b20710b3ffc9071b48a345cf640ec8c3a12b0b6266aacd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stringify-coder (version 3.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stringify-coder across your stack and pipelines.
If you installed it — respond
Remove stringify-coder 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 stringify-coder 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.
How O3 protects you
O3 blocks stringify-coder 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. stringify-coder on npm has been identified as a malicious package (version 3.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05953RLUA-2025-06492RLUA-2026-01596

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks stringify-coder-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