Which versions of dippy-invertor are malicious?

The following npm versions of dippy-invertor are flagged malicious: 35.1.6. Treat any of these as compromised.

How do I remediate dippy-invertor if I installed it?

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

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

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

Malicious package

dippy-invertornpm

dippy-invertor is a confirmed malicious npm package (MAL-2026-13276) that executes malicious code on install (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dippy-invertor (npm)

MAL-2026-13276

Immediate action

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

npm uninstall dippy-invertor

What this malware does

On require('dippy-invertor'), index.js unconditionally loads _ext.js, which downloads an OS-specific executable from four hardcoded Cloudflare Workers hosts (oob-worker.cf10*.workers.dev family) and, on HTTPS failure, falls back to a DNS-TXT covert channel against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru (queries TXT at c.<domain> for a chunk count, iterates 0.<domain>..N.<domain>, base64-decodes the concatenation). The retrieved payload is written to /tmp or %TEMP% under a disguised name (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached and unref'd via /bin/sh -c or cmd. Hostnames and the child_process / chmodSync API names are split-concatenated ([...].join('')) to evade string scanning, and cover-story identifiers (analytics_state, DISABLE_TELEMETRY, dotnet_diag_*.exe) disguise the loader. The package has no legitimate advertised behavior that requires fetching and executing an opaque remote binary at load time.

Malicious versions

1 flagged

35.1.6

Indicators of compromise (SHA-256)

e8dbed78de451c63784d37e7ae925bc4bf1288b7c4cf6e0e6fb0e7f9ff4cd451

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

Campaign

IN-MAL-2026-015715

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dippy-invertor-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