Which versions of dolyame-ui-tableinline are malicious?

The following npm versions of dolyame-ui-tableinline are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate dolyame-ui-tableinline if I installed it?

dolyame-ui-tableinline is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed dolyame-ui-tableinline — how do I know if it already compromised me?

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

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

Malicious package

dolyame-ui-tableinlinenpm

dolyame-ui-tableinline is a confirmed malicious npm package (MAL-2026-13600) that steals credentials and exfiltrates sensitive data (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-tableinline (npm)

MAL-2026-13600

Immediate action

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

npm uninstall dolyame-ui-tableinline

What this malware does

On require('dolyame-ui-tableinline'), index.js loads init.js which fetches a platform-specific native binary from obfuscated Cloudflare Workers mirrors (hostnames reconstructed at runtime via string-array.join("") to evade static matching), with a DNS TXT-record fallback to sdk.dl.wel1.ru. The binary is written to a disguised path under /tmp or %TEMP% (e.g., dotnet_diag<rand>.exe,.cache_<rand>), chmod 0755 on POSIX, and spawned detached via /bin/sh -c "<path> &" or cmd /c start /b. A TTL marker file rate-limits re-execution. A second dropper (base64 buffer -> chmod 755 -> /bin/sh -c spawn) is duplicated inside lib/telemetry.js, the declared main module, wrapped in a fake SDK scaffold. Opt-out env vars (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and cover-story file names (dotnet_diag_*,.analytics_state) are used as camouflage. The unpinned opaque native payloads, anonymous author-controlled hosts, obfuscated destination reconstruction, and detached background execution constitute full-host remote code execution on any machine that installs or imports the package.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

bb95d8006961e94a29fd7ca3fddf7769c9dc21c7bba268e0b3c699482876a9e8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-tableinline (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-tableinline across your stack and pipelines.
If you installed it — respond
dolyame-ui-tableinline is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dolyame-ui-tableinline 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 dolyame-ui-tableinline 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. dolyame-ui-tableinline on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016981

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-tableinline-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database