Which versions of transportator are malicious?

The following npm versions of transportator are flagged malicious: 1.0.1, 1.1.1. Treat any of these as compromised.

How do I remediate transportator if I installed it?

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

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

Yes — transportator is associated with the GHSA-6wwm-jx4f-p4xq, RLMA-2026-05339, RLUA-2026-05635 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 transportator 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 transportator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging transportator across your stack and pipelines.

Malicious package

transportatornpm

transportator is a confirmed malicious npm package (MAL-2026-5700) that executes malicious code on install (malicious versions 1.0.1, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in transportator (npm)

MAL-2026-5700

Immediate action

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

npm uninstall transportator

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.11.1.1

Indicators of compromise (SHA-256)

6f40d878023c5462d17916a03d22d7c2e9e1573ab590f50532aa2e620e7a5a13

a7a07b9b887c46913d32973cd0ad7f4e74e6a8af1ce7aa9ecff95607898e42be

9129a92eb5f81013cb62ad93225dd5d54a92d2fd7e2a1b95a4a656d07851200f

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 transportator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging transportator across your stack and pipelines.
If you installed it — respond
Remove transportator 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 transportator 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 transportator 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. transportator on npm has been identified as a malicious package (versions 1.0.1, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6wwm-jx4f-p4xqRLMA-2026-05339RLUA-2026-05635

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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