Which versions of dl-pp-latm are malicious?

The following npm versions of dl-pp-latm are flagged malicious: 80.4.2. Treat any of these as compromised.

How do I remediate dl-pp-latm if I installed it?

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

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

Yes — dl-pp-latm is associated with the IN-MAL-2026-009375 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 dl-pp-latm 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 dl-pp-latm (version 80.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dl-pp-latm across your stack and pipelines.

Malicious package

dl-pp-latmnpm

dl-pp-latm is a confirmed malicious npm package (MAL-2026-10086) that executes malicious code on install (malicious version 80.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dl-pp-latm (npm)

MAL-2026-10086

Immediate action

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

npm uninstall dl-pp-latm

What this malware does

Package [email protected] registers both preinstall and postinstall lifecycle hooks that run index.js, which collects installer machine identifiers — os.hostname(), os.userInfo().username, os.homedir(), dns.getServers(), current working directory, and the full package.json — and transmits them via HTTPS POST and DNS lookup to an Interactsh-style subdomain 'bvfmpadujgjgmbtzeibiikzijuhmtd2rs.oast.fun'. The package name pattern and 'Internal App bUg b0UntY gollum22' description match a dependency-confusion probe targeting internal/private package names; any developer workstation or CI system that resolves this package leaks internal hostnames, usernames, and DNS configuration to a third-party OOB collector. This fires automatically on npm install without user interaction.

Malicious versions

1 flagged

80.4.2

Indicators of compromise (SHA-256)

e21f1adb71c41838848c4d4292830a9738895d32a5b0f1f098e1efdadb233716

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

Campaign

IN-MAL-2026-009375

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dl-pp-latm-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