29 décembre 2024 | International, C4ISR, Sécurité

North Korean Hackers Deploy OtterCookie Malware in Contagious Interview Campaign

OtterCookie, a new JavaScript malware by North Korean hackers, steals data via Socket.IO and funds nuclear programs.

https://thehackernews.com/2024/12/north-korean-hackers-deploy-ottercookie.html

Sur le même sujet

  • Top Marine ‘signaling’ to industry that F-35 cuts are on the table

    3 avril 2020 | International, Aérospatial, Naval

    Top Marine ‘signaling’ to industry that F-35 cuts are on the table

    By: Aaron Mehta How will US Marines adjust for the future fight? | Reagan Defense Forum 2019 WASHINGTON — The top officer in the U.S. Marine Corps is sticking to the planned procurement of the F-35 joint strike fighter — but indicated a willingness to cut planes in the future if analysis says it makes sense. Marine Commandant Gen. David Berger told reporters Wednesday that he is a firm believer in the capabilities the F-35 is bringing, in particular the jump-jet B model favored by the service. However, Berger made it clear he's not wedded to long-term procurement plans, at a time the corps is shedding legacy missions as it pivots to focus to a primarily naval-focused service. “Right now, the program of record plows ahead as it is,” he said. “But I'm signaling to the industry, we have to be prepared to adjust as the operating environment adjusts. Right now, the program of record stays the same, but we will — we must — adapt to the adversary and we must adapt to the operating environment that we're challenged with being in.” Berger noted that an upcoming independent review of his force posture plans, expected to be completed in the next few months, could be a forcing function for more changes. Already, his planning guidance to the corps changed how many planes are featured in each F-35 squad, from 16 to 10. Longstanding plans call for the Marines to procure 353 of the F-35B and 67 of the F-35C carrier variants. “There's nothing like it,” Berger said of the jet. “The F-35B, the ability to operate from austere airfields and ships both, [is] incredible. In wargames, it's one of the handful of capabilities that really caused an adversary problems, because it is so flexible, it's deployable ashore or from ship. Gamechanger is sort of an overused phrase, but I'm a huge advocate of the F-35 and its capabilities.” Broadly speaking, Berger said, what will drive how many F-35s are in a squadron going forward, or how many the Corps eventually buys, comes down to maintenance — a longstanding issue for the stealthy jet. “If the maintenance readiness of the F-35 proves to be very, very strong, then of course, like any other system you need less of them because more of them are up all the time. On the other hand, if it turns out not to be so, then you're going to need more of them, to account for the ones that are in repair, that are down right now,” he said. Complicating that issue is what he called the “unique” supply chain for the jet, which in theory lets parts flow in from all over the world, as opposed to the traditional U.S. based supply. “In all aspects, we absolutely know we will learn along the way, and if its appropriate we will make adjustments” to either the squad level or the overall buy, Berger said. “But it's not a lack of confidence in the airframe at all.” https://www.defensenews.com/air/2020/04/01/top-marine-signaling-to-industry-that-f-35-cuts-are-on-the-table/

  • Pentagon requests 30-day extension for re-awarding JEDI

    12 août 2020 | International, C4ISR, Sécurité

    Pentagon requests 30-day extension for re-awarding JEDI

    Andrew Eversden WASHINGTON — The U.S. Department of Defense has requested 30 extra days to review vendor proposals as it prepares to make another award decision for its massive enterprise cloud contract, according to a Monday night court filing. The DoD is currently reviewing new revised proposals for its Joint Enterprise Defense Infrastructure contract, which it awarded to Microsoft over Amazon Web Services in October last year. In the filing, the DoD said that it “recently identified the need to reopen limited discussions related to certain aspects of the offerors' pricing proposals.” The request, made in the Court of Federal Claims, is yet another delay for the controversial JEDI cloud. The department was supposed to re-award the contract by Aug. 17 after receiving a 120-day stay to take corrective action on the contract. It's now asking to delay that decision to Sept. 16. “During the remand, DoD has identified areas of concern with respect to the revised proposals received from both offerors, resulting in multiple solicitation amendments, rounds of proposal revisions, and exchanges with the offerors,” the court filing said. AWS, which filed the protest late last year in the Court of Federal Claims after losing the contract, argues that the department made several technical errors while evaluating its proposal and also accuses President Donald Trump of political interference in the contract. AWS does not oppose the Pentagon's new motion, the court document said. In late July, DoD CIO Dana Deasy told reporters that the DoD would “probably sometimes towards the very end of August, barring any last minute, unforeseen additional issues that are raised.” The court filing says that the department “anticipates” that the re-evaluation process will wrap up in early September. The JEDI cloud has been delayed continuously throughout the entirety of the procurement process. Last year, the initial award decision was delayed for months due to a pre-award protest by Oracle. Earlier this year work on JEDI was further delayed when the court placed a temporary restraining order on any work on the JEDI cloud, finding that AWS was “likely to succeed” in proving DoD erred in the evaluation process. https://www.c4isrnet.com/battlefield-tech/it-networks/2020/08/11/pentagon-requests-30-day-extension-for-re-awarding-jedi/

  • Bradley Replacement: Did Army Ask For ‘Unobtainium’?

    24 janvier 2020 | International, Terrestre

    Bradley Replacement: Did Army Ask For ‘Unobtainium’?

    By SYDNEY J. FREEDBERG JR. WASHINGTON: For the third time in 11 years, the Army's attempt to replace the 1980s-vintage M2 Bradley ran afoul of the age-old tradeoff between armor and mobility, several knowledgeable sources tell Breaking Defense. The General Dynamics prototype for the Optionally Manned Fighting Vehicle – the only competitor left after other companies bowed out or were disqualified – was too heavy to meet the Army's requirement that a single Air Force C-17 cargo jet could carry two complete OMFVs to a war zone, we're told. But the vehicle had to be that heavy, GD's defenders say, to meet the Army's requirement for armor protection. Now, the Army hasn't officially said why it cancelled the current OMFV contract. Senior leaders – Chief of Staff, Gen. James McConville; the four-star chief of Army Futures Command, Gen. Mike Murray; and the civilian Army Acquisition Executive, Assistant Secretary Bruce Jette – have all publicly acknowledged that the requirements and timeline were “aggressive.” (Yes, all three men used the same word). Jette was the most specific, telling reporters that one vendor – which, from the context of his remark, could only be GD – did not meet all the requirements, but he wouldn't say which requirements weren't met. So, while we generally avoid writing a story based solely on anonymous sources, in this case we decided their track records (which we can't tell you about) were so good and the subject was so important that it was worth going ahead. “Industry told the Army the schedule was ‘unobtainium,' but they elected to proceed anyway,” one source told us: That's why the other potential competitors dropped out, seeing the requirements as too hard to meet. In particular, the source said, “industry needs more time to evaluate the trade [offs] associated with achieving the weight requirement.” With more time, industry might have been able to refine the design further to reduce weight, redesign major components to be lighter, or possibly – and this one is a stretch – even invent new stronger, lighter materials. But on the schedule the Army demanded, another source told us, reaching the minimum allowable protection without exceeding the maximum allowable weight was physically impossible. Why This Keeps Happening The Army's been down this road before and stalled out in similar ways. The Ground Combat Vehicle was too heavy, the Future Combat Systems vehicles were too light; “just right” still seems elusive. In 2009, Defense Secretary Bob Gates cancelled the Future Combat Systems program, whose BAE-designed Manned Ground Vehicles – including a Bradley replacement – had been designed to such strict weight limits that they lacked adequate armor. The Army had initially asked for the FCS vehicles to come in under 20 tons so one could fit aboard an Air Force C-130 turboprop transport. After that figure proved unfeasible, and the Air Force pointed out a C-130 couldn't actually carry 20 tons any tactically useful distance, the weight crept up to 26 tons, but the added armor wasn't enough to satisfy Gates' concerns about roadside bombs, then taking a devastating toll on US soldiers in Iraq. Four years later, amidst tightening budgets, the Army itself gave up on the Ground Combat Vehicle, another Bradley replacement, after strict requirements for armor protection drove both competing designs – from General Dynamics and BAE Systems – into the 56-70 ton range, depending on the level of modular add-on armor bolted onto the basic chassis. (A much-publicized Governmental Accountability Office study claimed GCV could reach 84 tons, but that was a projection for future growth, not an actual design). Not quite nine months ago, after getting initial feedback from industry on the Optionally Manned Fighting Vehicle, the Army made the tough call to reduce its protection requirements somewhat to make it possible to fit two OMFVs on a C-17. If our sources are correct, however, it didn't reduce the armor requirement enough for General Dynamics to achieve the weight goal. One source says that two of the General Dynamics vehicles would fit on a C-17 if you removed its modular armor. The add-on armor kit could then be shipped to the war zone on a separate flight and installed, or simply left off if intelligence was sure the enemy lacked heavy weapons. But the requirements didn't allow for that compromise, and the Army wasn't willing to waive them, the source said, because officers feared a vehicle in the less-armored configuration could get troops killed. Other Options Now, there are ways to protect a vehicle besides heavy passive armor. Some IEDs in Iraq were big enough to cripple a 70-ton M1 Abrams. Russian tanks get by with much lighter passive armor covered by a layer of so-called reactive armor, which explodes outwards when hit, blasting incoming warheads before they can penetrate. Both Russia and Israel have fielded, and the US Army is urgently acquiring, Active Protection Systems that shoot down incoming projectiles. The problem with both reactive armor and active protection is that they're only proven effective against explosive warheads, like those found on anti-tank missiles. They're much less useful against solid shells, and while no missile ever fielded can use those, a tank's main gun can fling solid shot with such force that it penetrates armor through sheer concentrated kinetic energy. (Protecting against roadside bombs and land mines is yet another design issue, because they explode from underneath, but it's no longer the all-consuming question it once ways. Advances in suspension, blast-deflecting hull shapes, and shock absorption for the crew have made even the four-wheeled Joint Light Tactical Vehicle remarkably IED-resistant and pretty comfortable). If the Army were willing to take the risk of relying more on active protection systems, or give industry more time to improve active protection technology, it could reduce its requirements for heavy passive armor. Or the Army could remove the soldiers from its combat vehicles entirely and operate them with a mix of automation and remote control, which would make crew protection a moot point. In fact, the service is investing in lightly-armored and relatively expendable Robotic Combat Vehicles – but it still sees those unmanned machines as adjuncts to humans, not replacements. As long as the Army puts soldiers on the battlefield, it will want the vehicles that carry them to be well-protected. Alternatively, the Army could drop its air transport requirements and accept a much heavier vehicle. Israel has already done this with its Namer troop carrier, a modified Merkava heavy tank, but then the Israel army doesn't plan to fight anywhere far away. The US, by contrast, routinely intervenes overseas and has dismantled many of its Cold War bases around the world. Air transport is a limited commodity anyway, and war plans assume most heavy equipment will either arrive by sea or be pre-positioned in warehouses on allied territory. But the Army really wants to have the option to send at least some armored vehicles by air in a crisis. If the Army won't give ground on either protection or transportability, then it faces a different dilemma: They need to either give industry more time to invent something revolutionary, or accept a merely evolutionary improvement. “We're going to reset the requirements, we're going to reset the acquisition strategy and timeline,” Gen. McConville said about OMFV on Tuesday. But, when he discussed Army modernization overall, he repeatedly emphasized that “we need transformational change, not incremental improvements. “Transformational change is how we get overmatch and how we get dominance in the future,” the Chief of Staff said. “We aren't looking for longer cords for our phones or faster horses for our cavalry.” https://breakingdefense.com/2020/01/bradley-replacement-did-army-ask-for-unobtainium

Toutes les nouvelles