{"id":7816,"date":"2026-04-02T14:49:49","date_gmt":"2026-04-02T14:49:49","guid":{"rendered":"https:\/\/www.securitytoday.de\/2026\/04\/02\/axios-npm-attack-how-a-hijacked-maintainer-account-threatened-millions-of-developers\/"},"modified":"2026-07-23T13:58:50","modified_gmt":"2026-07-23T13:58:50","slug":"axios-npm-attack-how-a-hijacked-maintainer-account-threatened-millions-of-developers","status":"publish","type":"post","link":"https:\/\/www.securitytoday.de\/en\/2026\/04\/02\/axios-npm-attack-how-a-hijacked-maintainer-account-threatened-millions-of-developers\/","title":{"rendered":"Axios npm Attack: Hijacked Maintainer Account Threatened&#8230;"},"content":{"rendered":"<p style=\"color:#69d8ed;font-size:0.9em;margin:0 0 16px;padding:0;\">8 min read<\/p>\n<p><strong>On 31 March 2026, security firm StepSecurity uncovered a remote-access Trojan (RAT) hidden in two tampered versions of the npm package Axios \u2013 one of the world\u2019s most-used JavaScript libraries, with more than 100 million weekly downloads. The attack weaponised a fake dependency, a hijacked maintainer account, and a command-and-control server to plant cross-platform backdoors on developers\u2019 machines. It ranks among the most sophisticated supply-chain strikes ever recorded in the npm ecosystem.<\/strong><\/p>\n<div style=\"background:#003340;color:#fff;padding:32px 36px;margin:32px 0;border-radius:8px;\">\n<p style=\"margin:0 0 18px 0;font-size:0.95em;font-weight:800;text-transform:uppercase;letter-spacing:0.2em;color:#69d8ed;border-bottom:2px solid rgba(105,216,237,0.25);padding-bottom:12px;\">Key Takeaways<\/p>\n<ul style=\"margin:0;padding-left:22px;color:rgba(255,255,255,0.92);line-height:1.6;\">\n<li style=\"margin-bottom:12px;color:rgba(255,255,255,0.92);\">Two tampered Axios releases (1.14.1 and 0.30.4) carried a cross-platform RAT smuggled in via the decoy dependency plain-crypto-js.<\/li>\n<li style=\"margin-bottom:12px;color:rgba(255,255,255,0.92);\">The attacker hijacked an npm maintainer account and bypassed the normal GitHub Actions release pipeline.<\/li>\n<li style=\"margin-bottom:12px;color:rgba(255,255,255,0.92);\">The RAT exfiltrates credentials such as AWS access keys and API tokens, then wipes its own traces after installation.<\/li>\n<li style=\"margin-bottom:12px;color:rgba(255,255,255,0.92);\">Microsoft Threat Intelligence and Google\u2019s Threat Intelligence Group attribute the campaign to North Korean actors (Sapphire Sleet \/ UNC1069).<\/li>\n<li style=\"color:rgba(255,255,255,0.92);\">Affected systems must be treated as fully compromised \u2013 simply deleting the RAT is not enough.<\/li>\n<\/ul>\n<\/div>\n<h2>What happened<\/h2>\n<p>Axios has been a staple JavaScript library for HTTP requests for more than a decade. Even though modern runtimes like Node.js and Deno now ship with the native Fetch API, millions of developers still prefer Axios for its friendlier API, automatic JSON parsing, and built-in interceptors. That popularity made it a prime target.<\/p>\n<p>On 30 March 2026 at 23:59 UTC, an attacker published version 4.2.1 of npm package plain-crypto-js \u2013 a lookalike of the legitimate and widely used crypto-js. Twenty-two minutes later, the poisoned Axios 1.14.1 appeared, tagged \u201clatest.\u201d At 01:00 UTC the same night, version 0.30.4 surfaced, tagged \u201clegacy.\u201d Both Axios builds declared plain-crypto-js as a new runtime dependency.<\/p>\n<p>The operation was meticulously staged. Eighteen hours earlier the attacker had released a harmless plain-crypto-js 4.2.0 \u2013 a decoy that would sail past automated scans. Only version 4.2.1 carried the actual payload.<\/p>\n<p>Normally Axios releases flow through GitHub Actions. The poisoned versions, however, were pushed directly from a compromised npm account. The attacker had seized control of lead maintainer jasonsaayman\u2019s account and swapped the registered e-mail for a ProtonMail address. Exactly how the account was hijacked remains unconfirmed as of April 2026.<\/p>\n<p>npm removed both malicious releases within roughly two to three hours. For a package clocking 100 million weekly downloads, even a few hours is a critical exposure window.<\/p>\n<div style=\"background:#fff8e1;border-left:4px solid #f5a623;padding:20px 24px;margin:32px 0;border-radius:0 8px 8px 0;\">\n<p style=\"margin:0 0 8px;font-weight:700;color:#c47f17;font-size:1.05em;\">Immediate action required<\/p>\n<p style=\"margin:0 0 8px;color:#444;line-height:1.6;\">Check your package.json for <strong>axios@1.14.1<\/strong> or <strong>axios@0.30.4<\/strong>. If <strong>plain-crypto-js<\/strong> appears in your node_modules, treat the host system as compromised.<\/p>\n<p style=\"margin:0;color:#444;line-height:1.6;\">Safe versions: <strong>axios@1.14.0<\/strong> and <strong>axios@0.30.3<\/strong>.<\/p>\n<\/div>\n<h2>Anatomy of the Attack: From postinstall Script to C2 Server<\/h2>\n<p>The source code of Axios itself contained no malicious code. The manipulation was limited to adding plain-crypto-js as a dependency in the package.json. Anyone auditing only the Axios code would have found nothing. The real weapon was hidden in the new dependency.<\/p>\n<p>The plain-crypto-js package included a postinstall script called setup.js. As soon as a developer ran npm install, a two-stage XOR-obfuscated JavaScript executed in the background \u2013 the so-called RAT dropper. It operated in four phases:<\/p>\n<p><strong>Phase 1 \u2013 System Detection:<\/strong> The script identifies the target system\u2019s operating system. macOS, Windows, and Linux are supported.<\/p>\n<p><strong>Phase 2 \u2013 Payload Download:<\/strong> The dropper establishes a connection to the command-and-control server (domain: sfrclak.com, IP: 142.11.206.73, port 8000). From there, a platform-specific binary is downloaded.<\/p>\n<p><strong>Phase 3 \u2013 Execution:<\/strong> The RAT is written to disk and launched. On macOS it lands as com.apple.act.mond in the Library Cache and is executed via \/bin\/zsh. On Windows it disguises itself as wt.exe (Windows Terminal) in %PROGRAMDATA% and uses a VBScript dropper. On Linux a Python RAT is downloaded to \/tmp\/ld.py and started in the background with nohup.<\/p>\n<p><strong>Phase 4 \u2013 Cleanup:<\/strong> The postinstall script deletes itself and replaces the package.json with the clean version 4.2.0. Running npm list then shows version 4.2.0. An npm audit finds no anomalies. The infection is active yet invisible.<\/p>\n<p>Once installed, the RAT gains access to everything on the compromised system: AWS credentials, OpenAI API keys, GitHub tokens, SSH keys, .env files with database passwords. In CI\/CD environments the impact can be even more severe: deployment credentials, signing keys, and access to production systems often reside there. A compromised build server can become the gateway to the entire infrastructure.<\/p>\n<p>StepSecurity discovered the attack via their AI Package Analyst and the runtime-monitoring tool Harden-Runner in instrumented GitHub Actions pipelines. The tool logs outgoing network connections during npm install and raised the alarm when an unknown C2 server was contacted.<\/p>\n<blockquote style=\"border-left:4px solid #69d8ed;margin:32px 0;padding:20px 24px;background:#fafafa;border-radius:0 8px 8px 0;font-size:1.1em;line-height:1.6;color:#333;\"><p>\n &#8220;The most important security tip has been to keep your packages up to date for years. Lately it feels like doing exactly that is the fastest way to get compromised.&#8221;<br \/>\n<cite style=\"display:block;margin-top:12px;font-size:0.8em;color:#888;font-style:normal;\">\u2013 Editorial note<\/cite>\n<\/p><\/blockquote>\n<h2>Why this attack is a new level of threat<\/h2>\n<p>Supply-chain attacks on npm aren\u2019t new. The 2018 event-stream incident went undetected for months and targeted crypto wallets. The 2021 compromise of ua-parser-js affected a package with seven million weekly downloads and distributed credential stealers. The 2022 sabotage of colors.js was a political protest by the maintainer themselves. Each of these incidents shook the ecosystem \u2013 and yet the Axios attack marks an escalation.<\/p>\n<div style=\"display:flex;gap:16px;margin:32px 0;flex-wrap:wrap;\">\n<div style=\"flex:1;min-width:180px;text-align:center;background:#f0f9fa;border-radius:12px;padding:24px 16px;border-top:3px solid #69d8ed;\">\n<div style=\"font-size:36px;font-weight:700;color:#69d8ed;letter-spacing:-0.03em;\">100 Mio.<\/div>\n<div style=\"font-size:14px;color:#444;margin-top:8px;\">Weekly Axios downloads on npm<\/div>\n<div style=\"font-size:11px;color:#888;margin-top:4px;\">npm Registry, March 2026<\/div>\n<\/p><\/div>\n<div style=\"flex:1;min-width:180px;text-align:center;background:#f0f9fa;border-radius:12px;padding:24px 16px;border-top:3px solid #69d8ed;\">\n<div style=\"font-size:36px;font-weight:700;color:#69d8ed;letter-spacing:-0.03em;\">2-3 hrs<\/div>\n<div style=\"font-size:14px;color:#444;margin-top:8px;\">Exposure window of malicious versions<\/div>\n<div style=\"font-size:11px;color:#888;margin-top:4px;\">StepSecurity, 31.03.2026<\/div>\n<\/p><\/div>\n<div style=\"flex:1;min-width:180px;text-align:center;background:#f0f9fa;border-radius:12px;padding:24px 16px;border-top:3px solid #69d8ed;\">\n<div style=\"font-size:36px;font-weight:700;color:#69d8ed;letter-spacing:-0.03em;\">3 platforms<\/div>\n<div style=\"font-size:14px;color:#444;margin-top:8px;\">macOS, Windows, Linux simultaneously affected<\/div>\n<div style=\"font-size:11px;color:#888;margin-top:4px;\">StepSecurity Incident Analysis<\/div>\n<\/p><\/div>\n<\/div>\n<p>The target is unprecedented: Axios is among the top ten most-used npm packages overall. A successful compromise could ripple out to hundreds of thousands of projects and CI\/CD pipelines worldwide.<\/p>\n<p>The sophistication far exceeds earlier attacks. Instead of injecting malicious code directly into the source, the attacker used a staged dependency-injection with time-delayed activation and automatic cleanup. After installation the system looked clean \u2013 a form of active camouflage that goes beyond passive hiding. StepSecurity logged the first C2 contact within two seconds of an npm install on an instrumented runner; without that automated monitoring the attack might have gone undetected for far longer.<\/p>\n<p>Comparing it to earlier npm incidents highlights the escalation: in the 2018 event-stream attack an attacker took over an abandoned package via social engineering and planted malicious code over months targeting Bitcoin wallets. In the 2021 ua-parser-js compromise the maintainer\u2019s account was hijacked and a credential stealer was distributed \u2013 similar to Axios, but without the multi-layer obfuscation or cross-platform payloads. The 2022 colors.js sabotage was a deliberate protest by the maintainer, not an external compromise.<\/p>\n<p>Attribution adds another layer: Microsoft Threat Intelligence ties the attack to the group Sapphire Sleet, while Google Threat Intelligence Group labels it UNC1069. Both point to North-Korean actors with financial motives. Elastic Security Labs identified overlaps between the macOS binary and WAVESHAPER, a known North-Korean backdoor. If confirmed, this would be the first documented case of a state actor compromising a top-100 npm package.<\/p>\n<h2>What IT teams must do now<\/h2>\n<p>The compromise affects more than just JavaScript developers. Every organisation that uses Axios in its projects or CI\/CD pipelines should prioritise the following steps:<\/p>\n<ol>\n<li><strong>Check versions:<\/strong> Inspect all package.json and lock files for axios@1.14.1 or axios@0.30.4. Immediately downgrade to 1.14.0 or 0.30.3 respectively.<\/li>\n<li><strong>Scan node_modules:<\/strong> Search for the package plain-crypto-js. If found, treat the system as compromised.<\/li>\n<li><strong>Inspect RAT artefacts:<\/strong> On macOS look for \/Library\/Caches\/com.apple.act.mond, on Windows for %PROGRAMDATA%\/wt.exe, on Linux for \/tmp\/ld.py.<\/li>\n<li><strong>Rotate credentials:<\/strong> Renew every API key, token and access credential on affected systems at once \u2013 AWS, OpenAI, GitHub, .env files.<\/li>\n<li><strong>Block C2:<\/strong> Block IP 142.11.206.73 and domain sfrclak.com at the network perimeter.<\/li>\n<li><strong>Secure CI\/CD:<\/strong> Make npm ci &#8211;ignore-scripts the default. Activate minimum-release-age policies so freshly published versions are not installed automatically.<\/li>\n<\/ol>\n<h2>The structural vulnerability remains<\/h2>\n<p>The Axios incident exposes a fundamental flaw in the npm ecosystem: a single account with a valid publish token can push malicious code to millions of systems. npm has made progress with Trusted Publishers and OIDC-based authentication \u2013 yet the attacker bypassed this very mechanism by taking over the maintainer account itself.<\/p>\n<p>For CISOs and IT-security teams the takeaway is clear: software-supply-chain security must command the same priority as network or endpoint security. Automated dependency monitoring, runtime analysis within CI\/CD pipelines and rigorous third-party-package policies are no longer nice-to-haves.<\/p>\n<p>Concretely, every organisation needs an up-to-date Software Bill of Materials (SBOM), automated alerts for unusual dependency changes and a clear policy governing how quickly new package versions may reach production. Consistently using lock files, disabling postinstall scripts in CI\/CD by default and configuring minimum-release-age policies are three measures that eliminate most of this attack surface. The next attack will not target Axios \u2013 yet it will exploit the same mechanics.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<p class=\"st-faq-hint\">Every question is locked. A tap unlocks the answer.<\/p>\n<details>\n<summary><strong>Am I affected if I use Axios?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Only if you have version 1.14.1 or 0.30.4 installed. All other versions are safe. Check your package.json and lock files (package-lock.json, yarn.lock, pnpm-lock.yaml).<\/p>\n<\/details>\n<details>\n<summary><strong>Is uninstalling the affected Axios version enough?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">No. If the RAT has already executed, it copied itself into system paths and deleted the postinstall script. Downgrading Axios alone will not remove the trojan. Treat the system as compromised and rotate all credentials.<\/p>\n<\/details>\n<details>\n<summary><strong>How was the maintainer account compromised?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">The exact attack vector remains unconfirmed as of April 2026. It is known that the npm account\u2019s registered e-mail address jasonsaayman was replaced with a ProtonMail address and the releases bypassed the regular GitHub Actions pipeline.<\/p>\n<\/details>\n<details>\n<summary><strong>Is there a CVE number for this incident?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">As of April 2026 no CVE has been assigned. Several security firms have documented the incident, but formal CVE assignment is still pending.<\/p>\n<\/details>\n<details>\n<summary><strong>Why didn\u2019t npm detect the malicious versions sooner?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">npm does not perform automated behavioural analysis at publish time. Packages are primarily scanned for known malware signatures. A postinstall script that contacts an external server is technically unremarkable \u2013 many legitimate packages use similar mechanisms for setup steps. Detection occurred through external monitoring, not npm\u2019s own safeguards.<\/p>\n<\/details>\n<details>\n<summary><strong>What can I do to mitigate supply-chain attacks in general?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Use lock files consistently, run npm ci instead of npm install in CI\/CD pipelines, enable &#8211;ignore-scripts for untrusted packages and adopt runtime-monitoring tools. A minimum-release-age policy prevents freshly published versions from being installed automatically. Teams should also maintain a Software Bill of Materials (SBOM) and set up automated alerts for dependency changes.<\/p>\n<\/details>\n<div style=\"background:#f0f9fa;border-radius:8px;padding:20px 24px;margin:24px 0;border-top:3px solid #69d8ed;\">\n<!--ST-LOWER-CARDS lang=en--><\/p>\n<h3 style=\"margin:48px 0 18px;padding-left:12px;font-size:1.05em;font-weight:800;color:#e6e3da;border-left:3px solid #69d8ed;line-height:1.2;\">Editor&#8217;s Picks<\/h3>\n<p><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/04\/01\/source-map-in-npm-package-how-anthropic-exposed-512000-lines-of-production-code\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/04\/pexels-security-lock-250x167.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Anthropic Exposed 512k Lines of Code via NPM Source Map<\/span><\/span><\/a><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/03\/29\/cisco-fmc-exploit-cve-2026-20131\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/03\/pexels-30965500-cisco-fmc-zero-day-250x167.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Cisco FMC Exploit: CVE-2026-20131<\/span><\/span><\/a><\/p>\n<h3 style=\"margin:48px 0 18px;padding-left:12px;font-size:1.05em;font-weight:800;color:#e6e3da;border-left:3px solid #69d8ed;line-height:1.2;\">More from the MBF Media Network<\/h3>\n<p><a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/04\/02\/ai-generated-terraform-code-is-the-cloud-stacks-biggest-unspoken-risk\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-ki-generierter-terraform-code-iac-sicher-86837703.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#0bb7fd;margin-bottom:5px;\">cloudmagazin<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">AI-Generated Terraform Code: The Cloud Stack\u2019s Hidden Risk<\/span><\/span><\/a><a href=\"https:\/\/www.digital-chiefs.de\/en\/healthcare-cio-2026-orchestrating-epa-ehds-and-nis2-simultaneously\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-healthcare-cio-epa-ehds-nis2-orchestrier-6266506-250x167.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#e8828d;margin-bottom:5px;\">Digital Chiefs<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Healthcare CIO 2026: Orchestrating ePA, EHDS, and NIS2 Simultaneously<\/span><\/span><\/a><a href=\"https:\/\/mybusinessfuture.com\/en\/13-3-million-people-retire-the-baby-boomer-gap-arrives\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-babyboomer-renteneintritt-demografie-lue-65687936-250x167.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#aa8ac2;margin-bottom:5px;\">MyBusinessFuture<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">13.3 million people retire: The baby boomer gap arrives<\/span><\/span><\/a><!--\/ST-LOWER-CARDS--><\/p>\n","protected":false},"excerpt":{"rendered":"North Korean hackers compromised two versions of the npm package Axios and injected a cross-platform remote access trojan. With over 100 million weekly downloads, a three-hour window was enough to demonstrate a new dimension of supply chain attacks.","protected":false},"author":50,"featured_media":15263,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_focuskw":"npm attack","_yoast_wpseo_title":"Axios npm Attack: How a Hijacked Maintainer Account Threatened Millions of Devel","_yoast_wpseo_metadesc":"Axios npm supply-chain attack: 2 tampered versions with RAT. Check what IT teams must verify and why npm remains structurally vulnerable.","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_yoast_wpseo_twitter-image-id":0,"evm_kih_original":false,"_evm_slot_owner":"","evm_cvss":0,"evm_risk":0,"evm_casefile":"","evm_primary_cve":"","evm_pin_until":0,"evm_external_preview_token":"","evm_external_preview_expires":"","_evm_translation_lang":"","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[255],"tags":[],"class_list":["post-7816","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-praxis-umsetzung-en"],"evm_reading_time_minutes":10,"wpml_language":"en","wpml_translation_of":7751,"_links":{"self":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/7816","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/users\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/comments?post=7816"}],"version-history":[{"count":9,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/7816\/revisions"}],"predecessor-version":[{"id":21636,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/7816\/revisions\/21636"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media\/15263"}],"wp:attachment":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media?parent=7816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/categories?post=7816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/tags?post=7816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}