Which versions of @datatrain/passenger are malicious?

The following npm versions of @datatrain/passenger are flagged malicious: 9.9.9, 9.9.10. Treat any of these as compromised.

How do I remediate @datatrain/passenger if I installed it?

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

If @datatrain/passenger 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 @datatrain/passenger part of a known attack campaign?

Yes — @datatrain/passenger is associated with the RLMA-2026-04708, RLUA-2026-05847 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 @datatrain/passenger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @datatrain/passenger (2 malicious versions).

Malicious package

@datatrain/passengernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@datatrain/passenger is a confirmed malicious npm package (MAL-2026-7065) that executes malicious code on install (malicious versions 9.9.9, 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @datatrain/passenger (npm)

MAL-2026-7065

Immediate action

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

npm uninstall @datatrain/passenger

Malicious versions

2 flagged

9.9.99.9.10

Indicators of compromise (SHA-256)

373ad809a1301d39496fc8eb027405c3163e41362f45b99abafc5d8f7febdf34

f1d1b82aabdfd115131757a3eead549ad9d0553cef84615181636ba7a5b89ef7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04708RLUA-2026-05847

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @datatrain/passenger-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