Which versions of text-transform-plus are malicious?

The following npm versions of text-transform-plus are flagged malicious: 1.2.4. Treat any of these as compromised.

How do I remediate text-transform-plus if I installed it?

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

If text-transform-plus 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 text-transform-plus part of a known attack campaign?

Yes — text-transform-plus is associated with the IN-MAL-2026-019480 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 text-transform-plus across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for text-transform-plus (version 1.2.4).

Malicious package

text-transform-plusnpm

Advisory published Sep 4, 2026Updated Sep 4, 2026

text-transform-plus is a confirmed malicious npm package (MAL-2026-15915) that executes malicious code on install (malicious version 1.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in text-transform-plus (npm)

MAL-2026-15915

Immediate action

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

npm uninstall text-transform-plus

What this malware does

The package's postinstall script downloads a ZIP archive from a hardcoded Dropbox URL (https://www.dropbox.com/scl/fi/djz38wdi1wks9j1h57zuv/coeur.zip) to a hidden randomized temp path, extracts it using unzip/Expand-Archive, and executes any.exe found on Windows with detached, hidden-window flags. The install script short-circuits when NODE_ENV=production or CI is set, and stages the payload under os.tmpdir() with dot-prefixed random names (.${Date.now()}.tmp, .data${Math.random()...}) to evade sandbox/CI environments and casual discovery. The declared purpose (a text-transform utility) has no need for any binary download or execution. The fetched binary is unpinned, unverified, and delivered from an anonymous file-sharing host, yielding arbitrary code execution on developer Windows machines at npm install time.

Malicious versions

1 flagged

1.2.4

Indicators of compromise (SHA-256)

e3efed1eeb185e17a51a67059e57156e5c540899e5a30076df710e0242a5560c

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-019480

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks text-transform-plus-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