Which versions of devplatform-s3-resources are malicious?

The following npm versions of devplatform-s3-resources are flagged malicious: 35.5.1. Treat any of these as compromised.

How do I remediate devplatform-s3-resources if I installed it?

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

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

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

Malicious package

devplatform-s3-resourcesnpm

devplatform-s3-resources is a confirmed malicious npm package (MAL-2026-12748) that executes malicious code on install (malicious version 35.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-s3-resources (npm)

MAL-2026-12748

Immediate action

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

npm uninstall devplatform-s3-resources

What this malware does

On load, index.js unconditionally requires./compat.js, which selects a platform-specific binary URL from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, cf103-070.workers.dev, cf102-baf.workers.dev), downloads the binary over HTTPS with a DNS-TXT covert-channel fallback that reassembles base64 chunks from TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, writes it to /var/tmp or %TEMP% under masquerading names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b with stdio ignored and windowsHide set. A stamp file at /tmp/.analytics_state (or %TEMP%\analytics_state) with a ~5.9h MAX_AGE dedupes re-executions across sessions. Endpoint hostnames are constructed by joining split string literals to evade static scanners, and CI opt-out checks are present to reduce detection in build environments. The package name resembles legitimate S3 tooling but the shipped code is a second-stage loader, not an S3 resource library.

Malicious versions

1 flagged

35.5.1

Indicators of compromise (SHA-256)

85d9e5338b835856fe3c5e45555c1a6bfbb6b7f412a83bbfaa0841813eeeeeb1

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

Campaign

IN-MAL-2026-015027

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-s3-resources-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